Hi,
Yeah, I can reproduce the problem on SMX 4.2.
I believe both of you encounter a cxf http-osgi transport issue which
is tracked by CXF-2947[1] and already get fixed.
Next SMX4.3 release will pick up this fix.
I can verify this fix on SMX4.3 snapshot kit I build locally.
[1]https://issues.apache.org/jira/browse/CXF-2947
Freeman
On 2010-10-15, at 下午6:46, Björn Bength wrote:
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.
--
Freeman Fang
------------------------
blog: http://freemanfang.blogspot.com
twitter: http://twitter.com/freemanfang
Open Source SOA: http://fusesource.com
Apache Servicemix:http://servicemix.apache.org
Apache Cxf: http://cxf.apache.org
Apache Karaf: http://karaf.apache.org
Apache Felix: http://felix.apache.org
