[jbossws-issues] [JBoss JIRA] (JBWS-3628) Add property expansion capability to .wsdl files
[
https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin....
]
R Searls commented on JBWS-3628:
--------------------------------
This will not work because CXF is inspecting the @WebService annotation to retrieve
path to the wsdl and then extracting the wsdl from the archive. There is no way
for us to pass information about an altered wsdl file written to disk or an InputStream
to said file.
I recommend we request cxf to allow us to pass a filter class through the bus extensions
map, that cxf runs immediately after they read the wsdl into the Definition class.
Our filter class will post process the contents of the Definition class before
subsequent cxf 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.6#6264)