[
https://jira.jboss.org/jira/browse/JBESB-2944?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-2944:
------------------------------
Description:
webservice_wsaddressing
webservice_wsproxy_basic
webservice_wsproxy_routed
webservice_wsproxy_security
webservice_wsproxy_versioning
webservice_wssecurity
wiretap
was:
webservice_wsaddressing
webservice_wsproxy_basic
webservice_wsproxy_routed
webservice_wsproxy_versioning
webservice_wssecurity
wiretap
Assignee: David Ward
Added "webservice_wsproxy_security" and assigned to me.
I grabbed this one first because yesterday Tom F. and I noticed a problem with the
InternalSOAPProxyWsdlLoader's use of JBossWS's internal SPI, where it is *still*
using an HttpConnection under-the-hood. This is an issue since on restart, Tomcat's
http connector might not be available yet. The same SPI is used as SOAPProcessor uses, so
I need to see if it's a problem there too, and if so, why we haven't heard about
it. I'll be creating a separate JIRA for it when I know a little more.
Verify quickstarts webservice_wsaddressing -> wiretap
-----------------------------------------------------
Key: JBESB-2944
URL:
https://jira.jboss.org/jira/browse/JBESB-2944
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.7
Reporter: Tom Fennelly
Assignee: David Ward
Fix For: 4.7
webservice_wsaddressing
webservice_wsproxy_basic
webservice_wsproxy_routed
webservice_wsproxy_security
webservice_wsproxy_versioning
webservice_wssecurity
wiretap
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira