dont think you can force everyone to use a specific class name or servlet mapping. i just dont think this goes well with what wicket is about.
this part of the spec may seem good when you are constructing a war from multiple submodules that you yourself own. in this case each submodule can provide its own config. eg the webmodule provides the wicket filter the jcr module provides the webdav servlet but i do not think this is good for generic frameworks because the configurations for those vary too widely across projects. -igor On Fri, Aug 14, 2009 at 6:24 PM, jluehe<jan.lu...@sun.com> wrote: > > If the applicationClassName init param is mandatory, then it should be > included with the wicket.Filter declaration in web-fragment.xml. Any > additional, optional init params could be specified with the wicket.Filter > declaration in web.xml. > > Jan > > > > igor.vaynberg wrote: >> >> thats the problem, it will error out because applicationClassName >> param is required. >> >> i just dont think this new fragment feature matches very well with how >> wicket is used. >> >> -igor >> >> On Thu, Aug 13, 2009 at 12:08 PM, arungupta<arun.gu...@gmail.com> wrote: >>> >>> 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 >>> >>> >> >> --------------------------------------------------------------------- >> 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-tp24916920p24980829.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
