[
https://issues.apache.org/jira/browse/CAMEL-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257766#comment-13257766
]
David Valeri commented on CAMEL-4279:
-------------------------------------
Interesting find with the timeout staying set. This seems to mean that the
Spring WS internal engine is being shared across endpoints. I'll look into
what is going on there. I'm wondering if this is a problem of unintentionally
shared Spring WS configuration across multiple endpoints. Why are those tests
@Ignore?
Re Sun HTTP Server. Do we have any builds that are run on non-Sun based JDKs?
You caught me being lazy here. I was on a plane when I wrote this and didn't
have docs for Jetty so I went with what I had available. I'll look into
changing it to use Jetty.
I don't think I will change AbstractHttpWebServiceMessageSenderDecorator. It
is a decorator of AbstractHttpWebServiceMessageSender classes. Aptly named
depending on how you look at it.
I'll look at the instanceof thing. I think that is likely stale code that
should have been refactored.
> 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
