-
Task
-
Resolution: Done
-
Major
-
None
-
None
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]:
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.
We need to clarify this a bit.
- is related to
-
JBWS-3810 Resolve "WARNING [org.apache.cxf.catalog.OASISCatalogManager]"
-
- Closed
-
