2 Replies Latest reply on Mar 11, 2011 3:20 AM by njiang

    cxfendpoint in camel

    tjain2011

      Please help me here

      I dont know what i am missing here:

       

      I am trying to create a simple cxf end point and use it my camel route and test it

       

      (ClassPathXmlApplicationContext.java:83)

           at org.pehz.flows.AppTest.createApplicationContext(AppTest.java:19)

           at org.pehz.flows.AppTest.createApplicationContext(AppTest.java:1)

           at org.apache.camel.test.junit4.CamelSpringTestSupport.setUp(CamelSpringTestSupport.java:50)

           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

           at java.lang.reflect.Method.invoke(Method.java:597)

           at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)

           at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)

           at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)

           at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)

           at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)

           at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)

           at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

           at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)

           at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)

           at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)

           at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)

           at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)

           at org.junit.runners.ParentRunner.run(ParentRunner.java:236)

           at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)

           at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)

           at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)

           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

           at java.lang.reflect.Method.invoke(Method.java:597)

           at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)

           at $Proxy0.invoke(Unknown Source)

           at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)

           at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)

           at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)

        • 1. Re: cxfendpoint in camel
          ffang

          Hi,

           

          Seems this is caused by cxf version mismatch.

           

          Which FUSE ESB version you are using?

          org.apache.cxf.jaxb.JAXBUtils.scanPackage method signature changed at the end of 2010.

          -    public static void scanPackages(Set<Class<?>> classes,

          +    public static void scanPackages(Set<Class<?>> classes,

          +                                    Class[] extraClass,

                                              Map<Package, CachedClass> objectFactoryCache) {

           

          Your bundle seems still use the old cxf/camel version but deployed into a FUSE ESB  version which already use new  scanPackages.

          Freeman

          • 2. Re: cxfendpoint in camel
            njiang

            Oh, you are running test with JUnit?

            Can you check your maven module dependencies ?

             

            Running "mvn dependency:tree" in your module will give us some useful information.