You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Arun Gupta <ar...@gmail.com> on 2009/08/11 14:46:44 UTC
Using Wicket in a Java EE 6 container
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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
HTML code for null values in AbstractSingleSelectChoice
Posted by Stefan Lindner <li...@visionet.de>.
Is there anything that stands against replacing
<option value=""></option>
with
<option value=""> </option>
For an empty option in a AbstractSingleSelectChoice? This would make an empty option valid in XHTML. ShallI open an issue o rare there any good reasons not to keep the current variant?
Stefan
Re: Using Wicket in a Java EE 6 container
Posted by Cserep Janos <cs...@szeretgom.hu>.
My understanding of Servlet 3.0 would suggest that if you want to go
without xml files, you would subclass WicketFilter and add
@ServletFilter and @InitParam annotations to your filter class.
j
2009/8/11 Major Péter <ma...@sch.bme.hu>:
> Hi,
>
> great article, but I have one concern:
> If the wicket team puts the web-fragment.xml in the library, then the
> application classname must be the same for every single wicket app? Or is it
> possible to override this parameter somewhere?
>
> Regards,
> Peter
>
> 2009-08-11 14:46 keltezéssel, Arun Gupta írta:
>>
>> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Major Péter <ma...@sch.bme.hu>.
Hi,
great article, but I have one concern:
If the wicket team puts the web-fragment.xml in the library, then the
application classname must be the same for every single wicket app? Or
is it possible to override this parameter somewhere?
Regards,
Peter
2009-08-11 14:46 keltezéssel, Arun Gupta írta:
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Major Péter <ma...@sch.bme.hu>.
And what if I'm wanna use WicketServlet instead of WicketFilter? I see
that this web-fragment.xml could be very useful for other frameworks,
but maybe it's not the best solution for Wicket. (It's just my opinion)
Anyway, wicket needs ~20-25 line in web.xml, is it really that
neccessary to pull apart these configurations?
Best Regards,
Peter Major
2009-08-14 01:30 keltezéssel, arungupta írta:
> I think the responsibilities are split.
>
> Wicket jar will provide the ServletFilter in web-fragment.xml and app will
> provide the filter parameter etc in web.xml.
>
> -Arun
>
>
> 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<ar...@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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Cserep Janos <cs...@szeretgom.hu>.
> Wicket jar will provide the ServletFilter in web-fragment.xml and app will
> provide the filter parameter etc in web.xml.
Small step for a man, one giant leap for someone else:).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by arungupta <ar...@gmail.com>.
I think the responsibilities are split.
Wicket jar will provide the ServletFilter in web-fragment.xml and app will
provide the filter parameter etc in web.xml.
-Arun
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<ar...@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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Using-Wicket-in-a-Java-EE-6-container-tp24916920p24962144.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Igor Vaynberg <ig...@gmail.com>.
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<Ja...@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<ar...@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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by jluehe <Ja...@Sun.COM>.
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<ar...@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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Igor Vaynberg <ig...@gmail.com>.
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<ar...@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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by arungupta <ar...@gmail.com>.
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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Igor Vaynberg <ig...@gmail.com>.
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<ar...@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<ar...@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by arungupta <ar...@gmail.com>.
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<ar...@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Igor Vaynberg <ig...@gmail.com>.
On Wed, Aug 12, 2009 at 7:49 PM, jluehe<Ja...@sun.com> wrote:
>
> As for the security concerns raised, note that configuration specified in
> web.xml always takes precedence over that specified in web-fragment.xml in
> case of a conflict.
if something mounts a filter on /asdasdasdasdasdasd that opens a
backdoor that wouldnt cause a conflict right? not unless i have
something also mapped onto that path...
> In addition, by setting metadata-complete to "true" in
> web.xml, any web-fragment.xml configuration will be ignored.
right, which kind of defeats the entire purpose...
oh well. hopefully this is just my ignorance of the spec.
-igor
>
> Jan
>
>
> 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<ar...@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wicket-in-a-Java-EE-6-container-tp24916920p24945876.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by jluehe <Ja...@Sun.COM>.
As for the security concerns raised, note that configuration specified in
web.xml always takes precedence over that specified in web-fragment.xml in
case of a conflict. In addition, by setting metadata-complete to "true" in
web.xml, any web-fragment.xml configuration will be ignored.
Jan
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<ar...@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Using-Wicket-in-a-Java-EE-6-container-tp24916920p24945876.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Using Wicket in a Java EE 6 container
Posted by Igor Vaynberg <ig...@gmail.com>.
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<ar...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org