I think it should be fine (but checking internally). Does it not depend upon how WicketFilter class handles it ?
How does it behave if this fragment is not there if it's not specified in web.xml per the current usage ? -Arun igor.vaynberg wrote: > > what happens if i dont have the > > <filter> > <filter-name>wicket.Filter</filter-name> > <init-param> > <param-name>applicationClassName</param-name> > > <param-value>org.glassfish.samples.WicketApplication</param-value> > </init-param> > </filter> > > piece in my web.xml? > > will that lead to an error? > > -igor > > On Wed, Aug 12, 2009 at 8:22 PM, arungupta<arun.gu...@gmail.com> wrote: >> >> The fragment can be easily split as: >> >> -- cut here -- >> <filter> >> <filter-name>wicket.Filter</filter-name> >> >> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class> >> </filter> >> -- cut here -- >> >> in web-fragment.xml >> >> and >> >> -- cut here -- >> <filter> >> <filter-name>wicket.Filter</filter-name> >> <init-param> >> <param-name>applicationClassName</param-name> >> >> <param-value>org.glassfish.samples.WicketApplication</param-value> >> </init-param> >> </filter> >> >> <filter-mapping> >> <filter-name>wicket.Filter</filter-name> >> <url-pattern>/*</url-pattern> >> </filter-mapping> >> -- cut here -- >> >> in web.xml. >> >> This keeps the Wicket registration in web-fragment.xml and the actual >> params >> in web.xml. >> >> -Arun >> >> >> igor.vaynberg wrote: >>> >>> 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 >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Using-Wicket-in-a-Java-EE-6-container-tp24916920p24948061.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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 > > > -- View this message in context: http://www.nabble.com/Using-Wicket-in-a-Java-EE-6-container-tp24916920p24957004.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
