We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
业务网关implements InvocationHandler,在反射中做rpc调用,但是升级servicecomb后 InvokerUtils.syncInvoke方法参数变了,这个有啥办法处理Object[] args 转成 <String, Object> swaggerArguments,尝试过将method中parameters的name做key,但是没发保证arg[]顺序和method入参一致
例如: public class Invoker implements InvocationHandler { @OverRide public Object invoke(Object proxy, Method method, Object[] args) { Object response = InvokerUtils.syncInvoke(microserviceName, microserviceSchemaId, microserviceOperationId,args); } }
The text was updated successfully, but these errors were encountered:
2.x 使用弱类型契约。 需要和 swagger 的参数匹配,而不是服务端的java代码参数匹配。
Sorry, something went wrong.
No branches or pull requests
业务网关implements InvocationHandler,在反射中做rpc调用,但是升级servicecomb后 InvokerUtils.syncInvoke方法参数变了,这个有啥办法处理Object[] args 转成 <String, Object> swaggerArguments,尝试过将method中parameters的name做key,但是没发保证arg[]顺序和method入参一致
例如:
public class Invoker implements InvocationHandler {
@OverRide
public Object invoke(Object proxy, Method method, Object[] args) {
Object response = InvokerUtils.syncInvoke(microserviceName,
microserviceSchemaId, microserviceOperationId,args);
}
}
The text was updated successfully, but these errors were encountered: