Hi,

could you please create a jira issue for this attaching the deployment archive (or slimmed down version of it, but still reproducing the problem), so that we can better analyse? Also, the code of the endpoint(s) might help, this is somehow related to some field's injection, looks very similar to something solved in the past (https://jira.jboss.org/jira/browse/JBAS-5359).

Thanks

I add the same probleme today trying to use camel and cxf in JBoss 5.1

I finally get in working excluding different artifact-id from my pom configuration

<properties>
        <cxf.version>2.2.6</cxf.version>
    </properties>

<dependencies>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.4</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-beans</artifactId>
            <version>2.5.6.SEC01</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-tx</artifactId>
            <version>2.5.6.SEC01</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-jms</artifactId>
            <version>2.5.6.SEC01</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-aop</artifactId>
            <version>2.5.6.SEC01</version>
            <exclusions>
                <exclusion>
                    <artifactId>aopalliance</artifactId>
                    <groupId>aopalliance</groupId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
            <version>2.5.6.SEC01</version>
            <scope>runtime</scope>
        </dependency>
       
        <dependency>
            <groupId>org.apache.cxf</groupId>
            <artifactId>cxf-rt-frontend-jaxws</artifactId>
            <version>${cxf.version}</version>
            <exclusions>
                <exclusion>
                    <artifactId>jaxb-impl</artifactId>
                    <groupId>com.sun.xml.bind</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>jaxb-api</artifactId>
                    <groupId>javax.xml.bind</groupId>
                </exclusion>
               
               
            </exclusions>
           
        </dependency>
        <dependency>
            <groupId>org.apache.cxf</groupId>
            <artifactId>cxf-rt-frontend-jaxrs</artifactId>
            <version>${cxf.version}</version>
            <exclusions>
                <exclusion>
                    <artifactId>xmlbeans</artifactId>
                    <groupId>org.apache.xmlbeans</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>jaxb-api</artifactId>
                    <groupId>javax.xml.bind</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>geronimo-stax-api_1.0_spec</artifactId>
                    <groupId>org.apache.geronimo.specs</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>geronimo-annotation_1.0_spec</artifactId>
                    <groupId>org.apache.geronimo.specs</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>jaxen</artifactId>
                    <groupId>jaxen</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>wsdl4j</artifactId>
                    <groupId>wsdl4j</groupId>
                </exclusion>
            </exclusions>
           
        </dependency>
        <dependency>
            <groupId>org.apache.cxf</groupId>
            <artifactId>cxf-rt-transports-http</artifactId>
            <version>${cxf.version}</version>
        </dependency>
        
        <dependency>
            <groupId>commons-logging</groupId>
            <artifactId>commons-logging</artifactId>
            <version>1.1.1</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-core</artifactId>
            <version>2.1.0</version>
            <exclusions>
                <exclusion>
                    <artifactId>commons-logging-api</artifactId>
                    <groupId>commons-logging</groupId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-spring</artifactId>
            <version>2.1.0</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-jms</artifactId>
            <version>2.1.0</version>
            <exclusions>
                <exclusion>
                    <artifactId>geronimo-jms_1.1_spec</artifactId>
                    <groupId>org.apache.geronimo.specs</groupId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-cxf</artifactId>
            <version>2.1.0</version>
            <exclusions>
                <exclusion>
                    <artifactId>cxf-rt-transports-http-jetty</artifactId>
                    <groupId>org.apache.cxf</groupId>
                </exclusion>
            </exclusions>
        </dependency>
    </dependencies>

There were pb with jetty, geronimo , jaxb hope this help

I had similar problem trying to deploy war-in-ear with webservices & (some of) apache CXF jars included in.

Similar exception appeared. When I included annotations-api.jar in the war file and turned on classloading isolation, the exception dissapeared and everything worked perfectly.

I suspect (not sure) that CXF has it's own mechanism of resource injection which uses @javax.annotation.Resource annotation, and all  properties annotated with @Resource aren't supposed to be injected by JBoss in deploytime, but exactly that happens.

If annotations-api.jar is present, and classloading isolation is on - then jboss will not detect @Resource annotations in cxf and will not try to inject them (because Resource.class from annotations-api.jar will overwrite Resource.class from jboss in CXF's classloader, and for JVM point of view, CXF's @Resource annotation will be different than jboss'es @Resource annotations).

I get the same error with CXF 2.2.9 and JBoss 6.0.0.M4.

The problem occurred with the following directory structure:

test.war

     WEB-INF

          lib

               cxf-2.2.9.jar

So just adding the CXF library to an empty war is enough to reproduce the problem.

I am afraid that class isolation solution may affect any other annotations that we may need JBoss to recognize in the war directory.  I think this is a bug that should be fixed in JBoss.

JBossAS 6.0.0.M4 comes with JBossWS-CXF stack installed. That means CXF libraries are already available and used on the server.

Generally speaking you don't need (and shouldn't) embedd cxf libraries anymore in your applications.

I tried today to upgrade my web service project from cxf 2.2.6 to 2.3.2 and I come up with the mapped-name is required for cxf....

I finally got it work adding geronimo-annotation_1.0_spec:

Here is my pom's dependencies for sharing :

<dependency>

       <groupId>org.apache.cxf</groupId>

       <artifactId>cxf-rt-frontend-jaxws</artifactId>

        <version>2.3.2</version>

     </dependency>

     <dependency>

       <groupId>org.apache.cxf</groupId>

       <artifactId>cxf-rt-transports-http</artifactId>

       <version>2.3.2</version>

     </dependency>

    <dependency>

       <groupId>org.apache.geronimo.specs</groupId>

        <artifactId>geronimo-annotation_1.0_spec</artifactId>

      <version>1.1.1</version>

    </dependency>

Had the exact same issue as Mr User. Philippe's solution solved it for me. Cheers!

I'm experiencing this same issue, on JBoss 5.1.0.EAP

Adding geronimo-annotation_1.0_spec doesn't seem like a very safe solution. i'd prefer to get the *real* solution.

Anyone know what the true cause of this is? I know AS 5.1.0.EAP doesn't have CXF libraries pre-bundled. Any ideas?

Confirmed with Redhat this is a JBoss 5 bug. There is a fix available on a later EAP version.

I ran into similar issue number of times while using cxf 2.3.2 on Jboss 5.1.0. Surprisingly, just changing the first line in web.xml to the following one resolved the issue:

<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:web="http://xmlns.jcp.org/xml/ns/javaee" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">