[jbossws-issues] [JBoss JIRA] (JBWS-3454) SOAP-over-JMS and AS7 remote connection factory integration

[ https://issues.jboss.org/browse/JBWS-3454?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3454: ---------------------------------- Description: 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. was: SOAP-over-JMS specs include 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 then read clients which are 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. -- 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