Hi David, As mentioned in the "code" list, I've added your first long term workaround. I agree that the second one would be even better, so I've entered a RFE:
"Improve setting of JAX-RS API implementation" http://restlet.tigris.org/issues/show_bug.cgi?id=767 Regarding the JAX-RS implementation, we definitely want to maintain it, complete it and upgrade to JAX-RS 1.1 when it is released. It's a strategic piece for the project, so no question about that. Stephan has lacked time in the past months due to a new job and moving into a new place. On my side, I've started to get more involved in the code of the extension but I've got so many other things to do that I would warmly welcome any help until Stephan can jump on this again. So, YES, your contributions would be welcome! :) Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : David Fogel [mailto:[email protected]] Envoyé : lundi 23 mars 2009 17:01 À : [email protected] Objet : Re: Restlet Jax-RS extension and OSGi Hi Stephan- Thanks for taking a look at this. Yes, I did see that it would be possible to get the Providers object injected into my resource classes. However I don't think that is the recommended way to accomplish this with Jax-Rs. (from what I remember, I think the Providers object is often meant to be injected into other Provider classes that need to make use of pre-existing Providers, but I'm not sure.) Is there any plan or timeframe for continuing development of the Restlet JAX-RS implementation? Would it make sense for me to put some time contributing some patches to this implementation? Thanks again, - Dave Fogel On Mon, Mar 23, 2009 at 4:37 AM, Stephan Koops <[email protected]> wrote: > Hi David, > > I've had no time to look into my own code or work with it, so I > forget, that the injection was changed. > Use a field (or parameter) of type javax.ws.rs.ext.Providers, annotate > it with @Context and use method getContextResolver(...) . > > I hope, that's the right solution. As said, I've long time no time to > keep me busy with Restlet and JAX-RS. Sorry for the wrong information first. > > best regards > Stephan ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=13905 77 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1429067
