[
https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin....
]
R Searls commented on JBWS-3628:
--------------------------------
A generic solution is for JBossWS to have a DefinitionVistor class that preforms
post-processing of an endpoint's javax.wsdl.Definition data before the wsdl data is
written by CXF. This utility would run after the return of super.doPublish(addr) and
before publishContractToFilesystem in org.jboss.wsf.stack.cxf.deployment.EndpointImpl.
We should not attempt to insert this processing into the CXF code base. The JAXB
processing
of this is quite deep in CXF's doPublish processing path. CXF is using the
com.ibm.wsdl.DefinitionImpl
of javax.wsdl.Definition which is another good reason not to muck with that code but to do
post processing.
Add property expansion capability to .wsdl files
------------------------------------------------
Key: JBWS-3628
URL:
https://issues.jboss.org/browse/JBWS-3628
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: david.boeren
Assignee: R Searls
Priority: Minor
Fix For: jbossws-cxf-5.0
The customer is doing JMS-based webservices using the following declarations in their
wsdl file (referred to using the wsdllocation annotation):
<soapjms:jndiConnectionFactoryName>myqueue</soapjms:jndiConnectionFactoryName>
<soapjms:jndiInitialContextFactory>com.vendor.InitialContextFactory</soapjms:jndiInitialContextFactory>
<soapjms:jndiURL>$MY_URL</soapjms:jndiURL>
The $MY_URL is the url of the messaging server. Since property replacement does not work
for wsdl files they need to manually modify this before deploying and package separate
versions of their app for each environment. If property expansion worked in the .wsdl
this would no longer be necessary.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)