On Thu, Aug 9, 2012 at 3:32 PM, Luca Masini <luca.masini(a)gmail.com&gt; wrote: Hi guys, I've found two things that are not standard jax-rs 1.1 1) web.xml: it registers only the servlet-mapping (2.3.2 of the specs), and this is not allowed Personally I think the plugin should be using the annotation @ApplicationPath instead of the web.xml entry. I know we've debated this before, but this approach brings it inline with what we do in JDF and it's really the recommended way of activating JAX-RS IMO. @ApplicationPath("/rest") public class JaxRsActivator extends Application { } (The path should be selected based on what the user specifies during setup). -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://google.com/profiles/dan.j.allen http://mojavelinux.com http://mojavelinux.com/seaminaction _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Hi Dan, I have added support for @ApplicationPath a long time ago already :-) The user have the choice between using @ApplicationPath or a servlet mapping. We should support both, because @ApplicationPath only works in real application server. Although I think everybody should use that, Forge shouldn't assume so. The two points mentioned by Luca are still very valid points though. Paul On Aug 10, 2012, at 1:49 , Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: On Thu, Aug 9, 2012 at 3:32 PM, Luca Masini <luca.masini(a)gmail.com&gt; wrote: > Hi guys, I've found two things that are not standard jax-rs 1.1 > > 1) web.xml: it registers only the servlet-mapping (2.3.2 of the specs), > and this is not allowed > Personally I think the plugin should be using the annotation @ApplicationPath instead of the web.xml entry. I know we've debated this before, but this approach brings it inline with what we do in JDF and it's really the recommended way of activating JAX-RS IMO. @ApplicationPath("/rest") public class JaxRsActivator extends Application { } (The path should be selected based on what the user specifies during setup). -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://google.com/profiles/dan.j.allen http://mojavelinux.com http://mojavelinux.com/seaminaction _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Hey Luca! By all means submit a JIRA Issue and send a pull request! We'd be *very* happy about that! ~Lincoln On Fri, Aug 10, 2012 at 3:18 AM, Luca Masini < luca.masini.mailing.list(a)gmail.com <javascript:_e({}, 'cvml', &#39;luca.masini.mailing.list(a)gmail.com&#39;);&gt;&gt; wrote: > Thank you Paul. > > Both are taken from the specs but while adding 3 lines to web.xml is not > a huge task, the fact that WebLogic and TomEE doesn't desploy RESTful > Services implemented by Stateful is blocking for me. > > > > 2012/8/10 Paul Bakker <paul.bakker.nl(a)gmail.com <javascript:_e({}, > 'cvml', &#39;paul.bakker.nl(a)gmail.com&#39;);&gt;&gt; > >> Hi Dan, >> >> I have added support for @ApplicationPath a long time ago already :-) >> The user have the choice between using @ApplicationPath or a servlet >> mapping. We should support both, because @ApplicationPath only works in >> real application server. Although I think everybody should use that, Forge >> shouldn't assume so. >> >> The two points mentioned by Luca are still very valid points though. >> >> Paul >> >> >> On Aug 10, 2012, at 1:49 , Dan Allen <dan.j.allen@gmail.com<javascript:_e({}, 'cvml', &#39;dan.j.allen(a)gmail.com&#39;);&gt;&gt; >> wrote: >> >> On Thu, Aug 9, 2012 at 3:32 PM, Luca Masini <luca.masini@gmail.com<javascript:_e({}, 'cvml', &#39;luca.masini(a)gmail.com&#39;);&gt; >> > wrote: >> >>> Hi guys, I've found two things that are not standard jax-rs 1.1 >>> >>> 1) web.xml: it registers only the servlet-mapping (2.3.2 of the specs), >>> and this is not allowed >>> >> >> Personally I think the plugin should be using the annotation >> @ApplicationPath instead of the web.xml entry. I know we've debated this >> before, but this approach brings it inline with what we do in JDF and it's >> really the recommended way of activating JAX-RS IMO. >> >> @ApplicationPath("/rest") >> public class JaxRsActivator extends Application { >> } >> >> (The path should be selected based on what the user specifies during >> setup). >> >> -Dan >> >> -- >> Dan Allen >> Principal Software Engineer, Red Hat | Author of Seam in Action >> Registered Linux User #231597 >> >> http://google.com/profiles/dan.j.allen >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org <javascript:_e({}, 'cvml', >> &#39;forge-dev(a)lists.jboss.org&#39;);&gt; >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org <javascript:_e({}, 'cvml', >> &#39;forge-dev(a)lists.jboss.org&#39;);&gt; >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> > > > -- > **************************************** > http://www.lucamasini.net > http://twitter.com/lmasini > http://www.linkedin.com/pub/luca-masini/7/10/2b9 > **************************************** > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org <javascript:_e({}, 'cvml', > &#39;forge-dev(a)lists.jboss.org&#39;);&gt; > https://lists.jboss.org/mailman/listinfo/forge-dev > > -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."