Hi Willem, yes, I'm using the CXF servlet transport. Here is my web.xml: http://pastie.org/2343749
Thanks, Mirko. On Tue, Aug 9, 2011 at 6:14 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Hi Mirko, > > Thanks for reporting this. It is looks like the CXF bus is created > differently between Camel > > When you import classpath:META-INF/cxf/cxf.xml in your application context, > an new CXF bus will be wired with the server factory bean, > > BTW, I know you are deploying the application context into a web container. > Which CXF transport are you using ? Are you using CXF servlet transport? It > can be helpful for me to dig the issue. > > Willem > > On 8/9/11 12:31 AM, Mirko Caserta wrote: >> >> Hi Willem, >> in preparing the test for a new issue I discovered that the problem is >> not at all camel related. >> >> For some reason, cxf is able to expose jaxws services in spring >> without having to declare: >> >> <import resource="classpath:META-INF/cxf/cxf.xml" /> >> >> The same is not true for jaxrs services. >> >> Because I had removed the above import statement in my spring context >> file, cxf was not being initialized as I was expecting, despite being >> able to expose the jaxws services. >> >> As to why the rest service was being exposed anyway when no spring >> import statement was present and camel 2.7.2 was being used, my guess >> is that something has changed in the initialization of the cxf bus >> between camel 2.7.2 and 2.8.0. >> >> To recap: my solution is to always use the cxf import statement above. >> >> Thanks for your support. >> >> Mirko >> >> On Sat, Aug 6, 2011 at 4:07 AM, Willem Jiang<willem.ji...@gmail.com> >> wrote: >>> >>> Hi Mirko, >>> >>> Just one module is OK, I can switch the Camel version to reproduce the >>> error. >>> The test application context could be a camel route with some JAXRS >>> endpoint >>> that you said. >>> >>> On 8/6/11 12:04 AM, Mirko Caserta wrote: >>>> >>>> Okay, I can do that. >>>> >>>> I only have to think how to reproduce the problem in a test. I'm >>>> afraid I'll have to provide a maven project with a couple modules, one >>>> which uses Camel 2.7.2 (that is supposed to work) and a specular one >>>> with Camel 2.8.0 which is supposed to fail... >>>> >>>> Does this sound right to you or can you think of a simpler way to let >>>> you reproduce the problem? >>>> >>>> Thanks, Mirko. >>>> >>>> On Fri, Aug 5, 2011 at 5:51 PM, Willem Jiang<willem.ji...@gmail.com> >>>> wrote: >>>>> >>>>> Hi Mirko, >>>>> >>>>> Can you create a simple test case and submit it to the Camel JIRA? >>>>> It will be helpful to help us locate the issue. >>>>> >>>>> On 8/5/11 4:12 PM, Mirko Caserta wrote: >>>>>> >>>>>> Hi Willem, >>>>>> thanks for answering. >>>>>> >>>>>> On Fri, Aug 5, 2011 at 3:48 AM, Willem Jiang<willem.ji...@gmail.com> >>>>>> wrote: >>>>>>> >>>>>>> Camel 2.8.0 is using CXF 2.4.x instead CXF 2.3.x. >>>>>>> Can you double check it ? >>>>>> >>>>>> I'm using CXF 2.4.1 in both cases. The funny thing is, CXF 2.4.1 with >>>>>> Camel 2.7.2 works fine. It's when I switch Camel to 2.8.0 that the >>>>>> rest endpoint disappears. >>>>>> >>>>>> Just to be clear, the only change between working and not working is >>>>>> modifying the corporate pom<dependencyManagement> block like >>>>>> this: >>>>>> >>>>>> http://pastie.org/2324098 >>>>>> >>>>>> and the<dependencies> block of my module like this: >>>>>> >>>>>> http://pastie.org/2324101 >>>>>> >>>>>>> BTW, can you access the jaxrs server successfully when you using >>>>>>> camel >>>>>>> 2.8.0? >>>>>> >>>>>> Nope. I get a "No service was found." page where i usually get an xml >>>>>> response. >>>>>> >>>>>> Any idea where to look further? I really wish to upgrade to 2.8.0 but >>>>>> this is a show stopper for me :/ >>>>>> >>>>>> Thanks anyway. >>>>>> >>>>>> Mirko >>>>>> >>>>>>> >>>>>>> On 8/4/11 11:26 PM, Mirko Caserta wrote: >>>>>>>> >>>>>>>> Hi there, >>>>>>>> I have a web app which exposes a cxf rest service via<jaxrs:server> >>>>>>>> and two soap endpoints with<cxf:cxfEndpoint>. >>>>>>>> >>>>>>>> The problem is, with camel 2.7.2, everything works okay. When I >>>>>>>> switch >>>>>>>> to camel 2.8.0, the<jaxrs:server> endpoint disappears and in >>>>>>>> the >>>>>>>> cxf >>>>>>>> servlet index which shows the available services I can only see the >>>>>>>> two soap endpoints listed. >>>>>>>> >>>>>>>> I read the release notes for camel 2.8.0 and I am adding >>>>>>>> camel-cxf-transport to my dependencies. >>>>>>>> >>>>>>>> Also, here is a diff of the jars which end up in WEB-INF/lib: >>>>>>>> >>>>>>>> http://pastie.org/2320248 >>>>>>>> >>>>>>>> Thanks in advance for your attention. >>>>>>>> >>>>>>>> Mirko >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Willem >>>>>>> ---------------------------------- >>>>>>> FuseSource >>>>>>> Web: http://www.fusesource.com >>>>>>> Blog: http://willemjiang.blogspot.com (English) >>>>>>> http://jnn.javaeye.com (Chinese) >>>>>>> Twitter: willemjiang >>>>>>> Weibo: willemjiang >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Willem >>>>> ---------------------------------- >>>>> FuseSource >>>>> Web: http://www.fusesource.com >>>>> Blog: http://willemjiang.blogspot.com (English) >>>>> http://jnn.javaeye.com (Chinese) >>>>> Twitter: willemjiang >>>>> Weibo: willemjiang >>>>> >>>> >>> >>> >>> -- >>> Willem >>> ---------------------------------- >>> FuseSource >>> Web: http://www.fusesource.com >>> Blog: http://willemjiang.blogspot.com (English) >>> http://jnn.javaeye.com (Chinese) >>> Twitter: willemjiang >>> Weibo: willemjiang >>> >> > > > -- > Willem > ---------------------------------- > FuseSource > Web: http://www.fusesource.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang > Weibo: willemjiang >
