Hi, for me it does not work with the latest version of cxf 2.4.1 nor with 2.3.5. It throws an exception cause of a missing namespace handler for jaxws, comes from somewhere deep in spring. With version 2.2.12 everything works fine. I also tried it with the cxf feature for karaf, no success.
They integrated the http-osgi transport into the normal http-transport (servlet) so most examples out there are not working with recent versions. I would appreciate hints for getting this working. Regards, Lars 2011/7/20 Freeman Fang <[email protected]> > Hi Brad, > > You may need take a look at cxf-jaxrs example shipped with Apache > Servicemix kit, it use cxf http-osgi transport(based on pax-web which use > OSGI HTTP service underlying). > You can download the kit from [1] > [1]http://repo2.maven.org/**maven2/org/apache/servicemix/** > apache-servicemix/4.3.0/<http://repo2.maven.org/maven2/org/apache/servicemix/apache-servicemix/4.3.0/> > > Freeman > > On 2011-7-20, at 上午4:00, Christian Schneider wrote: > > Hi Brad, >> >> you should take a look at the examples from Talend Service Factory (which >> is CXF + Karaf). >> >> For example this one: >> https://github.com/Talend/tsf/**tree/master/examples/jaxrs-**intro<https://github.com/Talend/tsf/tree/master/examples/jaxrs-intro> >> >> It shows how to use CXF on the OSGi container karaf. There is also a karaf >> distribution from Talend that is preconfigured for cxf: >> http://www.talend.com/**download_form.php?cont=sfact&**src=ResourcePage<http://www.talend.com/download_form.php?cont=sfact&src=ResourcePage> >> >> Alternatively you should also be able to use servicemix which is also >> preconfigured nicely for CXF. >> >> Compared to a raw Karaf both distros mostly adjust the jre.conf file to >> make CXF work. >> >> >> Christian >> >> >> Am 19.07.2011 20:46, schrieb Brad Taylor: >> >>> I am somewhat of a newbie to this whole process, and as such do not know >>> if >>> this question even makes sense. However let me try: >>> >>> I have a simple "application" that gets some simple arguments and >>> generates >>> essentially a result set of mutiple rows of identical data. What one >>> would >>> normally see as the result of a SQL SELECT. I wanted to have this be as >>> standalone as possible, however its main API is a URI (XML over HTTP). >>> So >>> from their I created an OSGI HTTP service (as opposed to embedding the >>> app >>> in a web container). So now I can deploy my standalone osgi container, >>> load >>> the osgi bundles needed, point my client to the listening port and get >>> back >>> results. >>> >>> So my next step was to change the API to a RESTful API. That is where I >>> started looking at Jersey, then CXF. However I can not find any examples >>> of >>> this type of implementation. >>> >>> Is this a valid approach? Or should I be looking at a different >>> approach? >>> If it is valid, would someone be so kind as to point me in a direction >>> that >>> may lead to my goal? >>> >>> Thank you >>> Brad Taylor >>> >>> >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> http://www.talend.com >> >> > ------------------------------**--------------- > Freeman Fang > > FuseSource > Email:[email protected] > Web: fusesource.com > Twitter: freemanfang > Blog: http://freemanfang.blogspot.**com <http://freemanfang.blogspot.com> > > > > > > > > > >
