RE: RIAP Client from within my J2EE application (jboss)

2009-08-16 Thread Jerome Louvel
://www.noelios.com -Message d'origine- De : Andrew Moore [mailto:rp.andrew.mo...@gmail.com] Envoyé : jeudi 30 juillet 2009 19:29 À : discuss@restlet.tigris.org Objet : Re: RIAP Client from within my J2EE application (jboss) I'm definitely still having issues... A little more

Re: RIAP Client from within my J2EE application (jboss)

2009-08-16 Thread Tim Peierls
On Sun, Aug 16, 2009 at 11:32 AM, Jerome Louvel jerome.lou...@noelios.comwrote: In your case, it seems that Application.getCurrent() returns null because the calling thread isn't the one that was initially processing the call, but a Quartz worker thread instead. I don't know enough about

Re: RIAP Client from within my J2EE application (jboss)

2009-07-30 Thread Andrew Moore
Thanks, I'll give that a shot and let you know if it works or what I'm still stuck on. Regards, Andrew -- View this message in context: http://n2.nabble.com/RIAP-Client-from-within-my-J2EE-application-%28jboss%29-tp3353312p3356788.html Sent from the Restlet Discuss mailing list archive at

Re: RIAP Client from within my J2EE application (jboss)

2009-07-30 Thread Andrew Moore
I'm definitely still having issues... A little more background: we have a quartz job that calls a class which is trying to make these requests. The Job class I created really has no context for the my restlet application. I'm not sure I'm creating my client correctly... when I create it like

RIAP Client from within my J2EE application (jboss)

2009-07-29 Thread Andrew Moore
Hi, We're running a J2EE app on JBOSS, but we've started integrating Restlet so that hopefully we can ditch our legacy app and move on with RESTful services. The short story is hopefully some other folks will be able to use our new Restlet service to get the resources they need, but if they

Re: RIAP Client from within my J2EE application (jboss)

2009-07-29 Thread Rob Heittman
Can you try riap://host instead of riap://component and see if that works for you? This is kind of cargo cult advice but we have mainly changed to that, and it works. Untested hypothesis: component/application context visibility issues (added for security reasons around 1.2M2 IIRC) prevent you