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> wrote:

On Thu, Aug 9, 2012 at 3:32 PM, Luca Masini <luca.masini@gmail.com> 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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev