Hi Brad, Let me get back to your original email,
>>> >>> 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. >>> Can you please clarify what examples are you looking for ? Would you like to see how OSGI HTTP Service can be used while deploying the bundles ? DOSGI offers one approach, example, see dosgi/greeter & dosgi/greeter_rest demos - those demos actually rely on embedded Jetty but can be switched to using HTTP services via the external configuration easily. Relying on CXF HTTP transport is another option. Do you prefer managing the lifecycle of (WS/RS) handlers directly ? Then I guess custom Activators can be used. Deploy slim war bundles is another option Cheers, Sergey >>> 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 >> >> > > > > -- > Sergey Beryozkin > > http://sberyozkin.blogspot.com > Talend - http://www.talend.com > -- Sergey Beryozkin http://sberyozkin.blogspot.com Talend - http://www.talend.com
