Re: Integrating JAX-RS runtime into DOSGi
Ok so that's it - perfect thanks Sergey On Aug 21, 2009, at 3:40 PM, Sergey Beryozkin wrote: Hi Have a look here please http://cxf.apache.org/distributed-osgi.html cheers, Sergey Demetris G wrote: Hey Sergei and Josh Is the DOSGi you are referring in the essay of an email below the Masters thesis I read once (and it became an open source branch of an apache project) or is this a separate design? We worked on a design calked p2pSOA the connected distributed OSGi containers over p2p technologies while exposing the endpt bundles as web services. So I am fairly interested in your discussion - I just want a quick clarification so I can position your work in my mind. Thanks On Aug 21, 2009, at 12:28 PM, "Sergey Beryozkin" wrote: Hi Josh Can you please let me know if JAXB is being used for your JAX-RS endpoints ? I've spotted that for HTTP Service based JAX-RS endpoints no AegisProvider is being set - I'would actually like JAXB being used by default for JAXRS endpoints which will be consistent with the expectations of JAX-RS users in general - but I'd like to confirm first that JAXB is working ok in your case... thanks, Sergey Sergey, Thanks again for the detailed documentation you've provided in this thread. I was able to easily convert from JAX-WS to JAX-RS, which (I think) will make our lives even easier. Once we've got the ability to expose a single service with both of these frontends, I'll make use of that as well. I agree that the jaxrs.resource property is no longer needed, as you can simply register jaxrs resources as a dosgi services. Josh On Sat, Jun 20, 2009 at 11:10 AM, Sergey Beryozkin wrote: Hi, I've applied your patch and I've completed the initial integration of JAX-RS into DOSGi RI. As it often happens I underestimated a bit how long it would take me to do it :-) but I'm quite happy now with what has been done so far. I haven't got a chance to write JAX-WS system tests yet - I was a bit constrained in time but judging from the code you did JAXWS/ databindings should be working nicely now - please feel free to add a system test, or either of us will do it asap. Now, the property names have actually changed and differ from those you provided in the patch. As David noted, it was recommended that DOSGI providers would use reverse domain names as prefixes to their custom configuration types, such as 'pojo' in case of DOSGI RI. Furthermore, 'pojo' was a bit constraining in that it did not reflect the fact that say SOAP or RS services were supported. Additionally, the DOSGI way is -- View this message in context: http://www.nabble.com/RE%3A-Integrating-JAX-RS-runtime-into-DOSGi-tp24127832p25086130.html Sent from the cxf-dev mailing list archive at Nabble.com.
Re: Handling collections with Aegis in JAX-RS
Ha - I am in Waltham on the line of Lexington and Waltham close to IBM. How funny is that man. On Aug 21, 2009, at 2:36 PM, Benson Margulies wrote: Lexington, MA, outside of Boston. On Fri, Aug 21, 2009 at 2:26 PM, D G wrote: You are a funny man Benson - do you mind if I ask where you are located? On Aug 21, 2009, at 2:14 PM, Benson Margulies wrote: I are at whole foods with iPhone - will engage when I get home. On Aug 21, 2009, at 1:28 PM, "Sergey Beryozkin" > wrote: This one testWriteTo(org.apache.cxf.jaxrs.provider.AegisProviderTest) also fails Hudson provides some strange info http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-Trunk-JDK15/676/ shows that Benson's changes has made it into the build but http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-Trunk-JDK15/676/org.apache.cxf$cxf-rt-frontend-jaxrs/ shows that no changes has been applied Sergey - Original Message - From: "Daniel Kulp" To: Cc: "Benson Margulies" Sent: Friday, August 21, 2009 6:22 PM Subject: Re: Handling collections with Aegis in JAX-RS On Fri August 21 2009 12:52:32 pm Benson Margulies wrote: It appears to be you. I ran mvn in rt/databinding/aegis again, and still no hate mail from hudson as well. No. He's refering to the org.apache.cxf.jaxrs.provider.AegisJSONProviderTest in the jaxrs frontend. Dan On Fri, Aug 21, 2009 at 12:39 PM, Sergey Beryozkin wrote: Hi Benson I'm seeing all the Aegis write tests failing at the momentOr is it only me ? cheers, Sergey - Original Message - From: "Benson Margulies" To: Sent: Friday, August 21, 2009 5:00 PM Subject: Re: Handling collections with Aegis in JAX-RS All fixed now. I finally remembered the history of this. When you first inveigled me into working up the Aegis provider, I got as far as this test, and sent you email saying, 'OK, you fix the test, and I'll work out the rest of the kinks.' And then if you even fixed up the test I missed the email, so I never went back to it. -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Handling collections with Aegis in JAX-RS
You are a funny man Benson - do you mind if I ask where you are located? On Aug 21, 2009, at 2:14 PM, Benson Margulies wrote: I are at whole foods with iPhone - will engage when I get home. On Aug 21, 2009, at 1:28 PM, "Sergey Beryozkin" wrote: This one testWriteTo(org.apache.cxf.jaxrs.provider.AegisProviderTest) also fails Hudson provides some strange info http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-Trunk-JDK15/676/ shows that Benson's changes has made it into the build but http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-Trunk-JDK15/676/org.apache.cxf$cxf-rt-frontend-jaxrs/ shows that no changes has been applied Sergey - Original Message - From: "Daniel Kulp" To: Cc: "Benson Margulies" Sent: Friday, August 21, 2009 6:22 PM Subject: Re: Handling collections with Aegis in JAX-RS On Fri August 21 2009 12:52:32 pm Benson Margulies wrote: It appears to be you. I ran mvn in rt/databinding/aegis again, and still no hate mail from hudson as well. No. He's refering to the org.apache.cxf.jaxrs.provider.AegisJSONProviderTest in the jaxrs frontend. Dan On Fri, Aug 21, 2009 at 12:39 PM, Sergey Beryozkin> wrote: > Hi Benson > > I'm seeing all the Aegis write tests failing at the momentOr is it > only me ? > > cheers, Sergey > > - Original Message - From: "Benson Margulies" > > To: > Sent: Friday, August 21, 2009 5:00 PM > Subject: Re: Handling collections with Aegis in JAX-RS > >> All fixed now. >> >> I finally remembered the history of this. When you first inveigled me >> into working up the Aegis provider, I got as far as this test, and >> sent you email saying, 'OK, you fix the test, and I'll work out the >> rest of the kinks.' And then if you even fixed up the test I missed >> the email, so I never went back to it. -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Integrating JAX-RS runtime into DOSGi
Hey Sergei and Josh Is the DOSGi you are referring in the essay of an email below the Masters thesis I read once (and it became an open source branch of an apache project) or is this a separate design? We worked on a design calked p2pSOA the connected distributed OSGi containers over p2p technologies while exposing the endpt bundles as web services. So I am fairly interested in your discussion - I just want a quick clarification so I can position your work in my mind. Thanks On Aug 21, 2009, at 12:28 PM, "Sergey Beryozkin" wrote: Hi Josh Can you please let me know if JAXB is being used for your JAX-RS endpoints ? I've spotted that for HTTP Service based JAX-RS endpoints no AegisProvider is being set - I'would actually like JAXB being used by default for JAXRS endpoints which will be consistent with the expectations of JAX-RS users in general - but I'd like to confirm first that JAXB is working ok in your case... thanks, Sergey Sergey, Thanks again for the detailed documentation you've provided in this thread. I was able to easily convert from JAX-WS to JAX-RS, which (I think) will make our lives even easier. Once we've got the ability to expose a single service with both of these frontends, I'll make use of that as well. I agree that the jaxrs.resource property is no longer needed, as you can simply register jaxrs resources as a dosgi services. Josh On Sat, Jun 20, 2009 at 11:10 AM, Sergey Beryozkin >wrote: Hi, I've applied your patch and I've completed the initial integration of JAX-RS into DOSGi RI. As it often happens I underestimated a bit how long it would take me to do it :-) but I'm quite happy now with what has been done so far. I haven't got a chance to write JAX-WS system tests yet - I was a bit constrained in time but judging from the code you did JAXWS/ databindings should be working nicely now - please feel free to add a system test, or either of us will do it asap. Now, the property names have actually changed and differ from those you provided in the patch. As David noted, it was recommended that DOSGI providers would use reverse domain names as prefixes to their custom configuration types, such as 'pojo' in case of DOSGI RI. Furthermore, 'pojo' was a bit constraining in that it did not reflect the fact that say SOAP or RS services were supported. Additionally, the DOSGI way is
