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

AbstractAddressingEndpointMapping not calling SmartEndpointInterceptor.shouldIntercept while creating invocation chain [SWS-883] #959

Closed
gregturn opened this issue Dec 4, 2014 · 3 comments
Assignees
Milestone

Comments

@gregturn
Copy link
Contributor

gregturn commented Dec 4, 2014

Nate Stoddard opened SWS-883* and commented

AbstractAddressingEndpointMapping adds all SmartEndpointInterceptors to its SoapEndpointInvocationChain without calling shouldIntercept() on each instance. Contract this to AbstractEndpointMapping which does call shouldIntercept() on each interceptor and only adds ones that return true to its chain.

AbstractAddressingEndpointMapping should be enhanced to invoke shouldIntercept and only add the necessary SmartEndpointInterceptors to its SoapEndpointInvocationChain.


Affects: 2.2.0.RELEASE

Reference URL: http://stackoverflow.com/questions/27276302/whats-the-proper-way-of-configuring-a-soapactionsmartendpointinterceptor-along

Referenced from: pull request #27

@gregturn
Copy link
Contributor Author

gregturn commented Dec 5, 2014

Arjen Poutsma commented

PR at #27

@gregturn
Copy link
Contributor Author

gregturn commented Dec 5, 2014

@gregturn
Copy link
Contributor Author

gregturn commented Dec 5, 2014

Greg Turnquist commented

@arjen No problem. Thanks!

@gregturn gregturn added this to the 2.2.1 milestone Sep 22, 2020
@gregturn gregturn self-assigned this Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant