This behaviour is not specific to cxfrs but also any cxf endpoint. We have noticed that the service (in the soap case) still appear to work ok, but we can no longer access the wsdl by appending ?wsdl. /Bjorn
On Fri, Oct 15, 2010 at 11:02 AM, Auke <[email protected]> wrote: > > I have some issues with bundles that make use of the cxfrs component. I can > reproduce with the given example as well: > > 1. install examples-cxf-jaxrs feature > > 2. Go to http://localhost:8181/cxf/crm/customerservice/customers/123 > http://localhost:8181/cxf/crm/customerservice/customers/123 and see the > correct result. > > 3. update the corresponding 'Apache ServiceMix Example :: CXF JAX-RS OSGI' > bundle. > > 4. Go to http://localhost:8181/cxf/crm/customerservice/customers/123 > http://localhost:8181/cxf/crm/customerservice/customers/123 and see a 404. > > Incidentally if you look at the http://localhost:8181/cxf/ > http://localhost:8181/cxf/ response in both cases it changes from: > > Endpoint address: http://localhost:8181/cxf/crm > WADL : http://localhost:8181/cxf/crm?_wadl&type=xml > > into > > Endpoint address: /crm > WADL : /crm?_wadl&type=xml > > Any ideas? > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/REST-service-stops-working-when-updating-bundle-with-cxfrs-bean-route-tp3213372p3213372.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
