That is true but, for example, how I use it at work is. I build every service as a jsr181 service unit, then if I need that service to be a web service I build the http service unit for it, if not, components just talk soap between each other (I use soap not rest, but would be nice to have a similar model for rest). I just came up with the idea of using this model, so if I'm doing something terribly bad with it feel free to tell me :)
Eduardo Burgos On Tue, May 13, 2008 at 2:59 PM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > The big problem is that it gives no additional features and make the thing > much more complex: the rest component would only be able to support http > and it may require hacking the JAX-RS implementation to be able to rebuild > a correct request (not sure about that). > Honestly, while I think the jsr181/http or cxf-bc/cxf-se combination > works great, > having native support for JAX-WS and JAX-RS is much cleaner imho. > > On Tue, May 13, 2008 at 5:11 PM, Eduardo Burgos <[EMAIL PROTECTED]> wrote: > > Why not make it like the old JSR-181 component? make the HTTP component > > forward calls to the REST component? That way other services can make > calls > > to it without going through HTTP. > > > > > > > > > > > > On Fri, May 9, 2008 at 11:31 AM, Guillaume Nodet <[EMAIL PROTECTED]> > wrote: > > > > > JAX-RS is about annotating POJOs to expose them as web resources. > > > I guess it should not be too difficult to do that in ServiceMix, but > my > > > question > > > is more about how you want to bridge with JBI ? Will your rest pojo > send > > > exchanges into the NMR ? Do you expect this service to be exposed on > the > > > NMR ? > > > > > > The problem is kinda the same as with JAX-WS, but even more difficult > to > > > apply > > > to the JBI way of thinking: for JAX-WS, we use two components, one > > > containing > > > the jaxb2/jaxws annotations (cxf-se service engine) and another one > > > containing the > > > transport informations in the wsdl (cxf-bc). But with JAX-RS, lots > > > of transport > > > informations use annotations, and there's no real way to use another > > > transport. > > > So I think the best way would in SMX4 to support REST pojos exposed > > > through > > > the osgi http service (or another http transport), which should be > > > quite straightforward, > > > but I'm not sure if/how we could have services calling those POJOs > > > without going > > > through HTTP. > > > > > > On Fri, May 9, 2008 at 5:21 PM, Ryan Moquin <[EMAIL PROTECTED]> > > > wrote: > > > > Go figure, if I wanted to add a JAX-RS interface to a JBI component, > am > > > I > > > > better off putting a servlet to proxy requests into a CXF > webservice? > > > Or am > > > > I better off have an HTTP request come in through servicemix-http > and > > > > parsing the path into operations myself? I saw a mention of REST > pojos > > > on > > > > the servicemix site, but I wasn't sure how to go about trying it > out. I > > > > think I'm trying to figure out how REST fits in with JBI as well as > an > > > > access mechanism :) > > > > > > > > On Fri, May 9, 2008 at 11:16 AM, Guillaume Nodet <[EMAIL PROTECTED]> > > > wrote: > > > > > > > >> On Fri, May 9, 2008 at 5:14 PM, Guillaume Nodet <[EMAIL PROTECTED]> > > > wrote: > > > >> >> A quick question on 3.2.2, will it the cxf rest support at all? > Or > > > is > > > >> that > > > >> >> planned for another release? > > > >> > > > > >> > CXF 2.1 will be integrated in ServiceMix 3.3 > > > >> > > > > >> > > > >> Btw, I'm not sure what you expect by REST support, but JAX-RS does > not > > > >> fit very well with JBI, > > > >> but this integration is planned for ServiceMix 4.x. > > > >> > > > >> -- > > > >> Cheers, > > > >> Guillaume Nodet > > > >> ------------------------ > > > >> Blog: http://gnodet.blogspot.com/ > > > >> > > > > > > > > > > > > > > > > -- > > > Cheers, > > > Guillaume Nodet > > > ------------------------ > > > Blog: http://gnodet.blogspot.com/ > > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >
