dont think so because a) not everyone wants to name their application class org.glassfish.samples.WicketApplication b) not everyone wants to use /* mapping
i havent read the spec yet but just from looking at the article this is a little troubling from security perspective. just because i add a jar to my app it can now register a servlet behind my back and create a backdoor into the server? -igor On Tue, Aug 11, 2009 at 5:46 AM, Arun Gupta<arun.gu...@gmail.com> wrote: > I wrote a blog describing how to use Wicket with a Servlet 3.0/Java EE > 6 container: > > http://blogs.sun.com/arungupta/entry/totd_91_applying_java_ee > > Any chance the changes can be integrated in the wicket-*.jar ? > > -Arun > > -- > Need Application Server ? - Download glassfish.org > Blog: http://blogs.sun.com/arungupta > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
