[JBoss JIRA] (JBWS-3628) Add property expansion capability to .wsdl files
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3628:
----------------------------------
Attachment: JBWS-3628.diff
Attaching JBWS-3628.diff patch file for adding a XMLStreamReaderWrapper into the CXF WSDLManagerImpl. The wrapper makes CXF use a custom StreamReaderDelegate to read wsdl docs before passing them to wsdl4j.
The delegate expands system properties in attribute and element values.
CXF 3.0.1 is required (CXF-5866).
We need a testcase for verification; if there's need to set a system property on server side for testing purpose, the RemoteDeployer should be extended to allow doing that. See https://docs.jboss.org/author/display/AS71/CLI+Recipes#CLIRecipes-Adding%... for recipies on setting system props in the model.
> 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
>
> Attachments: JBWS-3628-JBossWS-WSDLFactory-tentative-patch.txt, JBWS-3628-tentative-patch-from-Rebecca.txt, JBWS-3628.diff
>
>
> 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)
9 years, 9 months
[JBoss JIRA] (JBWS-3811) Upgrade to Apache CXF 3.0.1
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3811:
-------------------------------------
Summary: Upgrade to Apache CXF 3.0.1
Key: JBWS-3811
URL: https://issues.jboss.org/browse/JBWS-3811
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Fix For: jbossws-cxf-5.0
Upgrade to Apache CXF 3.0.1 as soon as it's out.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (JBWS-3810) Resolve "WARNING [org.apache.cxf.catalog.OASISCatalogManager]"
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3810?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3810:
----------------------------------
Fix Version/s: jbossws-cxf-5.0
> Resolve "WARNING [org.apache.cxf.catalog.OASISCatalogManager]"
> ---------------------------------------------------------------
>
> Key: JBWS-3810
> URL: https://issues.jboss.org/browse/JBWS-3810
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: R Searls
> Assignee: R Searls
> Priority: Minor
> Fix For: jbossws-cxf-5.0
>
>
> With the move to cxf 3.0.0 we are seeing these warnings.
> 10:03:35,013 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}SecurityService from WSDL: WEB-INF/wsdl/SecurityService.wsdl
> 10:03:35,016 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/rsearls/j1/wfly9-alessio-cxf-3/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
> 10:03:35,016 WARNING [org.apache.cxf.catalog.OASISCatalogManager]
> (MSC service thread 1-7) Catalog found at
> jar:file:/home/rsearls/j1/wfly9-alessio-cxf-3/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/
> modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws.jar
> !/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found.
> Check the classpatch for an xmlresolver jar.
> These warning messages, "WARNING [org.apache.cxf.catalog.OASISCatalogManager]" are
> occurring because the module dependencies for org.apache.xml-resolver is not declared
> in modules/system/layers/base/org/apache/cxf/main/module.xml. The dependency is
> declared in modules/system/layers/base/org/apache/cxf/impl/main/module.xml but does
> not appear to be needed by this module.
> Updating modules/system/layers/base/org/apache/cxf/main/module.xml will resolve the warnings.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (JBWS-3788) Add catalog testcase
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3788?page=com.atlassian.jira.plugin.... ]
R Searls commented on JBWS-3788:
--------------------------------
These warning messages, "WARNING [org.apache.cxf.catalog.OASISCatalogManager]" are
occurring because the module dependencies for org.apache.xml-resolver is not declared
in modules/system/layers/base/org/apache/cxf/main/module.xml. The dependency is
declared in modules/system/layers/base/org/apache/cxf/impl/main/module.xml but does
not appear to be needed by this module.
I've created https://issues.jboss.org/browse/JBWS-3810 to address these warnings.
> Add catalog testcase
> --------------------
>
> Key: JBWS-3788
> URL: https://issues.jboss.org/browse/JBWS-3788
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: R Searls
> Fix For: jbossws-cxf-5.0
>
>
> We need a testcase that explicitly verifies usage of jaxws catalog both in the jbossws-cxf-client jar / jaxws-client module and in a user deployment.
> As a consequence of having moved to Apache CXF 3.0.0 (JBWS-3686), I'm seeing warnings like the following because of the change at [1]:
> {noformat}
> 10:48:16,235 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-4) Catalog found at jar:file:/dati/jboss-as-7.2.0.Final/build/target/jboss-as-7.2.0.Final/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
> 10:48:16,235 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-4) Catalog found at jar:file:/dati/jboss-as-7.2.0.Final/build/target/jboss-as-7.2.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
> {noformat}
> We need to clarify this a bit.
> [1] https://github.com/apache/cxf/commit/7823e995
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (JBWS-3810) Resolve "WARNING [org.apache.cxf.catalog.OASISCatalogManager]"
by R Searls (JIRA)
R Searls created JBWS-3810:
------------------------------
Summary: Resolve "WARNING [org.apache.cxf.catalog.OASISCatalogManager]"
Key: JBWS-3810
URL: https://issues.jboss.org/browse/JBWS-3810
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: R Searls
Assignee: R Searls
Priority: Minor
With the move to cxf 3.0.0 we are seeing these warnings.
10:03:35,013 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}SecurityService from WSDL: WEB-INF/wsdl/SecurityService.wsdl
10:03:35,016 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/rsearls/j1/wfly9-alessio-cxf-3/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
10:03:35,016 WARNING [org.apache.cxf.catalog.OASISCatalogManager]
(MSC service thread 1-7) Catalog found at
jar:file:/home/rsearls/j1/wfly9-alessio-cxf-3/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/
modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws.jar
!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found.
Check the classpatch for an xmlresolver jar.
These warning messages, "WARNING [org.apache.cxf.catalog.OASISCatalogManager]" are
occurring because the module dependencies for org.apache.xml-resolver is not declared
in modules/system/layers/base/org/apache/cxf/main/module.xml. The dependency is
declared in modules/system/layers/base/org/apache/cxf/impl/main/module.xml but does
not appear to be needed by this module.
Updating modules/system/layers/base/org/apache/cxf/main/module.xml will resolve the warnings.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (JBWS-3741) WebService doesn't support "//"
by Thomas Szadel (JIRA)
[ https://issues.jboss.org/browse/JBWS-3741?page=com.atlassian.jira.plugin.... ]
Thomas Szadel commented on JBWS-3741:
-------------------------------------
My bad!
I looked at JBoss EAP 6.3 and effectively, the issue is resolved in that version !
Thanks !
> WebService doesn't support "//"
> --------------------------------
>
> Key: JBWS-3741
> URL: https://issues.jboss.org/browse/JBWS-3741
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.1.3
> Reporter: Thomas Szadel
> Assignee: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-cxf-4.3
>
>
> The WebService part of Jboss eap 6 doesn't support double slash ('//') in URI (although JBoss 5 supports it and the Web connector also supports it).
> That's to say, those 3 urls should represent the same one :
> * http://localhost:8080/ws/myWs?wsdl
> * http://localhost:8080/ws//myWs?wsdl
> * http://localhost:8080//ws/myWs?wsdl
> BUT only the first one is accepted by JBoss. The others raise that stack trace:
> javax.servlet.ServletException: JBWS024029: Cannot obtain destination for /ws//myWs
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:170)
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:87)
> org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
> org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:150)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
> org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> AND if I call the following URL, it works : http://localhost:8080/./ws/myWs?wsdl
> IMHO, the method org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination should use a "canonical path" before testing the equality.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (JBWS-3741) WebService doesn't support "//"
by Thomas Szadel (JIRA)
[ https://issues.jboss.org/browse/JBWS-3741?page=com.atlassian.jira.plugin.... ]
Thomas Szadel commented on JBWS-3741:
-------------------------------------
I tried to add "<module name="javax.servlet.api" />" in module.xml of org.jboss.ws.jaxws-client.
Then, I got the following exception :/ (/ws/myWs is correctly resolved)
javax.servlet.ServletException: JBWS024029: Cannot obtain destination for /ws//myWs
org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:166)
org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:83)
org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:133)
org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:211)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136)
org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> WebService doesn't support "//"
> --------------------------------
>
> Key: JBWS-3741
> URL: https://issues.jboss.org/browse/JBWS-3741
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.1.3
> Reporter: Thomas Szadel
> Assignee: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-cxf-4.3
>
>
> The WebService part of Jboss eap 6 doesn't support double slash ('//') in URI (although JBoss 5 supports it and the Web connector also supports it).
> That's to say, those 3 urls should represent the same one :
> * http://localhost:8080/ws/myWs?wsdl
> * http://localhost:8080/ws//myWs?wsdl
> * http://localhost:8080//ws/myWs?wsdl
> BUT only the first one is accepted by JBoss. The others raise that stack trace:
> javax.servlet.ServletException: JBWS024029: Cannot obtain destination for /ws//myWs
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:170)
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:87)
> org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
> org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:150)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
> org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> AND if I call the following URL, it works : http://localhost:8080/./ws/myWs?wsdl
> IMHO, the method org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination should use a "canonical path" before testing the equality.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (JBWS-3741) WebService doesn't support "//"
by Thomas Szadel (JIRA)
[ https://issues.jboss.org/browse/JBWS-3741?page=com.atlassian.jira.plugin.... ]
Thomas Szadel reopened JBWS-3741:
---------------------------------
It still doesn't work with JBoss EAP 6.2.3.
Now, I have that stack trace (invalid module configuration?) :
javax.servlet.ServletException: JBWEB000248: Servlet execution threw an exception
java.lang.NoClassDefFoundError: javax/servlet/ServletException
org.jboss.wsf.stack.cxf.Messages_$bundle.cannotObtainDestinationFor(Messages_$bundle.java:399)
org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:166)
org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:83)
org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:133)
org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:211)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136)
org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
JBWEB000071: root cause
java.lang.ClassNotFoundException: javax.servlet.ServletException from [Module "org.jboss.ws.jaxws-client:main" from local module loader @3d533528 (finder: local module finder @21c6f48c (roots: D:\jboss-eap-6.2\modules,D:\jboss-eap-6.2\modules\system\layers\base))]
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213)
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459)
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408)
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389)
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134)
org.jboss.wsf.stack.cxf.Messages_$bundle.cannotObtainDestinationFor(Messages_$bundle.java:399)
org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:166)
org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:83)
org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:133)
org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:211)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136)
org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> WebService doesn't support "//"
> --------------------------------
>
> Key: JBWS-3741
> URL: https://issues.jboss.org/browse/JBWS-3741
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.1.3
> Reporter: Thomas Szadel
> Assignee: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-cxf-4.3
>
>
> The WebService part of Jboss eap 6 doesn't support double slash ('//') in URI (although JBoss 5 supports it and the Web connector also supports it).
> That's to say, those 3 urls should represent the same one :
> * http://localhost:8080/ws/myWs?wsdl
> * http://localhost:8080/ws//myWs?wsdl
> * http://localhost:8080//ws/myWs?wsdl
> BUT only the first one is accepted by JBoss. The others raise that stack trace:
> javax.servlet.ServletException: JBWS024029: Cannot obtain destination for /ws//myWs
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:170)
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:87)
> org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
> org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:150)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
> org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> AND if I call the following URL, it works : http://localhost:8080/./ws/myWs?wsdl
> IMHO, the method org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination should use a "canonical path" before testing the equality.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months