Re: [jetty-users] Enabling annotations per webapp

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

Check your jetty version again.

There once was a Jetty 2.5.1, but its ancient. (think pre servlet api days)

--

Joakim Erdfelt <joakim@xxxxxxxxxxx>

webtide.com - intalio.com/jetty

Expert advice, services and support from from the Jetty & CometD experts

eclipse.org/jetty - cometd.org

On Fri, Jan 24, 2014 at 11:55 AM, Jim Garrison <jim.garrison@xxxxxxxx> wrote:

Using Jetty 2.5.1

The doc at http://www.eclipse.org/jetty/documentation/current/annotations.html says

> Jetty supports the servlet specification annotations. It is not enabled by default,
> so the following sections show you how to enable it, and how to use them
>
> Quick Setup
>
> If you are using the standard distribution of Jetty, and want to enable processing of
> annotation for all your webapps, edit the $JETTY_HOME/start.ini file and uncomment
> the following lines...

But later in http://www.eclipse.org/jetty/documentation/current/using-annotations.html it says

> By default, Jetty will scan all classes from WEB-INF/classes, and all jars from WEB-INF/lib
> according to the order, if any, established by absolute or relative ordering clauses in web.xml.

This seems self-contradictory.  If I want to use annotations such as @WebServlet, do I need the start.ini file or can annotation scanning be turned on per webapp, and if so, how?
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users