JBoss Community

Re: Using apache cxf.xml with a jax-ws client

created by Daniel Cote in JBoss Web Services - View the full discussion

Hi Alessio,

 

 

I did the test, using the following configuration:

 

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">

    <deployment>

        <dependencies>

            <module name="com.oracle" export="true" />

            <module name="com.logibec.parameters" export="true" /> <!-- parameters -->

<!--

            <module name="org.apache.cxf.impl" export="true">

             <imports>

                <include path="META-INF"/>

                <include path="META-INF/cxf"/>

              </imports>

              <exports>

                <include path="META-INF"/>

                <include path="META-INF/cxf"/>

              </exports>

            </module>         

            <module name="org.apache.cxf" export="true">

              <imports>

                <include path="META-INF"/>

                <include path="META-INF/cxf"/>

              </imports>

              <exports>

                <include path="META-INF"/>

                <include path="META-INF/cxf"/>

              </exports>

            </module>           

            <module name="org.springframework.spring" export="true">

              <imports>

                <include path="META-INF"/>

              </imports>

              <exports>

                <include path="META-INF"/>

               </exports>

            </module>           

  -->    

 

              <module name="org.jboss.ws.cxf.jbossws-cxf-client" export="true">

              <imports>

                <include path="META-INF"/>

              </imports>

              <exports>

                <include path="META-INF"/>

               </exports>

            </module>           

               

        </dependencies>

    </deployment>

</jboss-deployment-structure>

 

The problem, with this configuration, is that it makes MANDATORY to have an META-INF/cxf/cxf.xml (which I did not managed to setup).

Here the trace file:

 

06:54:28,996 INFO (http-localhost-127.0.0.1-8080-1) org.apache.cxf.bus.spring.BusApplicationContext.prepareRefresh Refreshing org.apache.cxf.bus.spring.BusApplicationContext@5cf70001: startup date [Thu Mar 14 06:54:28 EDT 2013]; root of context hierarchy

06:54:29,043 FINE (http-localhost-127.0.0.1-8080-1) org.apache.cxf.bus.spring.TunedDocumentLoader.<clinit> FastInfoset not found on classpath. Disabling context load optimizations.

06:54:29,043 INFO (http-localhost-127.0.0.1-8080-1) org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Loaded configuration file cxf.xml.

06:54:29,058 FINE (http-localhost-127.0.0.1-8080-1) org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Creating application context with resources: [class path resource [META-INF/cxf/cxf.xml], class path resource [cxf.xml]]

06:54:29,058 INFO (http-localhost-127.0.0.1-8080-1) org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]

06:54:29,058 WARN (http-localhost-127.0.0.1-8080-1) org.apache.cxf.bus.spring.SpringBusFactory.createApplicationContext Initial attempt to create application context was unsuccessful.: org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [META-INF/cxf/cxf.xml]; nested exception is java.io.FileNotFoundException: class path resource [META-INF/cxf/cxf.xml] cannot be opened because it does not exist

at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)

at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.internalLoadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:154)

at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.access$000(ControlledValidationXmlBeanDefinitionReader.java:66)

...

 

In my understanding, this resource should be made optionnal.

Anyway, thanks again.

 

Ciao

Reply to this message by going to Community

Start a new discussion in JBoss Web Services at Community