[
https://issues.apache.org/jira/browse/CAMEL-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259608#comment-13259608
]
David Valeri commented on CAMEL-4279:
-------------------------------------
Like you said, the @Ignore tests should use an embedded service. The tests can
be made to work like the one I added for the SSL stuff (that is after the use
of the Sun HTTP server is dealt with). I'll probably do this when I move the
SSL tests to use Jetty.
A user is only forced to use different WebServiceTemplates if they provide one
explicitly and use a setting in the endpoint URI that would alter the internal
state of the WebServiceTemplate (right now that is timeout and SSL). If they
don't provide one, a new WebServiceTemplate is created for each endpoint and
the timeout/SSL/etc. setting of one endpoint does not affect the setting of
another endpoint.
We cannot move the prepareMessageSenders call back to where it was before
because there is a concurrency issue there. If we move it back, we would have
to make sure that only one thread is using a WebServiceTemplate at a given time
or accept that, under load, weird and unpredictable behavior will happen when
using the timeout setting in Camel. The synchronization would mean that only
one producer endpoint among all the endpoints that share a WebServiceTemplate
could be sending a message at any given time.
Neither of those options are desirable. We are either introducing a bottle
neck or allowing the system to have unpredictable behavior.
I would imagine that most users are not providing a custom WebServiceTemplate
when they use this component. Providing it is an advanced use case, and I feel
that it is fine to expect the advanced user to deal with timeout and/or SSL on
their own if they are providing their own WebServiceTemplate. Adding the
timeout URI option and SSL options to the endpoint URI parameters is a
convenience for the majority of use cases where the user just needs a basic Web
service client. The return on our investment for improved user experience
diminishes rapidly if we try to make the timeout and SSL URI parameters
universally applicable for more advanced use cases.
> Add support for the new TLS for spring-ws if possible
> -----------------------------------------------------
>
> Key: CAMEL-4279
> URL: https://issues.apache.org/jira/browse/CAMEL-4279
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
> Affects Versions: 2.8.0
> Reporter: Claus Ibsen
> Assignee: David Valeri
> Labels: security
> Fix For: 2.10.0
>
>
> David do you mind checking if its possible to add support for the new TLS you
> did, for spring-ws component as well?
> See nabble
> http://camel.465427.n5.nabble.com/need-some-advice-on-cxf-or-spring-ws-tp4643001p4643001.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
