Skip to content
New issue

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

Fine-tune HTTP/RMI Invoker exception handling [SPR-15684] #20243

Closed
spring-issuemaster opened this issue Jun 20, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Jun 20, 2017

Juergen Hoeller opened SPR-15684 and commented

RemoteInvocationSerializingExporter has a few flaws in its exception handling: getProxy() should throw an IllegalStateException instead of IllegalArgumentException and avoid building its normally unused exception message upfront. Furthermore, doReadRemoteInvocation should include descriptive type information for a non-matching invocation object (and analogously in AbstractHttpInvokerRequestExecutor.doReadRemoteInvocationResult for the result object).


No further details from SPR-15684

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.