Hi JS, I also ran into the need to include the leading "/cxf" in the @Path annotation when putting together a CXF JAX-RS feature and demo for SMX4 (patch submitted attached to https://issues.apache.org/activemq/browse/SMX4-279).
Obviously we discussed this same issue on previous threads on the SMX and CXF mailing lists. Can you raise a JIRA for this and assign it to me? I'll investigate putting in a work-around either in the SMX cxf-transports-osgi logic that makes the target URI known to JAX-RS, or else in the URI pattern matching logic in CXF JAX-RS layer itself. Cheers, Eoghan 2009/5/4 jsbournival <[email protected]>: > > I have a serious issue that I want to discuss. > > I am developing rest services osgi bundles on fuse4/smx4 using the cxf-osgi > transport. JAX-RS impl is obviously CXF, which is fine. But as I > http://www.nabble.com/Re%3A-Deploying-REST-service-on-CXF-Transport-for-OSGi-fails-p23164246.html > learned recently , I have to specify "/cxf" as part of my implementation > @Path annotation, like this: > > > @Path("/cxf/top10") > public class TopTenRestService { > // methods > } > > > I find this somewhat strange because it exposes (shall I say binds) the > underlying JAX-RS implementation to my service class, which is the complete > opposite of what the JAX-RS spec should provide. > > Again, maybe I just don't get it. Using it this way actually works, but > there's something not right about how to specifiy the @Path. > > As a complement, here is my service configuration in my bundle' spring bean > file. Maybe you'll find something I'm doing wrong: > > > > > > > > > > > > > > > > > So, are there any plans to correct this? Is this an issue? If so, shall I > expect a quick fix, or a long refactor phase? > > Thank you, > > JS. > -- > View this message in context: > http://www.nabble.com/Deploying-REST-service-on-CXF-Transport-for-OSGi-tp23371703p23371703.html > Sent from the cxf-user mailing list archive at Nabble.com. >
