[
https://issues.jboss.org/browse/JBWS-3454?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3454:
----------------------------------
Summary: Additional tests for SOAP-over-JMS and AS7 remote connection factory
(was: SOAP-over-JMS and AS7 remote connection factory integration)
Issue Type: Task (was: Feature Request)
Description: (was: SOAP-over-JMS spec includes means for specifying (in the wsdl)
the connection factory to be used for looking up the queue/topic associated to the
endpoint. That connection factory reference is read by clients which are then most likely
performing remote jndi lookup.
The work around AS7-1338 added remote JNDI support to AS7, but that's provided through
different (remotely exported) connection factories. Given the JBossWS-CXF SOAP-over-JMS
impl integration is fully contract driven, we need a mechanism for allowing users to
advertise remote JNDI references (remote connection factory, remote jndi url, etc.) while
having the endpoint use locally available connection factory.)
Changing this jira into a testsuite/documentation one; the use of local connection factory
during deploy and publishing of remote ones is to be achieved by properly writing multiple
service wsdl contracts. It's not possible to reliably guess the currently configured
local connection factory jndi name.
Additional tests for SOAP-over-JMS and AS7 remote connection factory
--------------------------------------------------------------------
Key: JBWS-3454
URL:
https://issues.jboss.org/browse/JBWS-3454
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-4.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira