You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by MZ...@osc.state.ny.us on 2010/03/25 19:22:42 UTC
WicketFilter Config
Due to the fact that SpringWebApplication is deprecated, we evaluated
several ways of configuring Wicket using WicketFilter. I found
ContextParamWebApplicationFactory to work with a Spring Annotation
approach. SpringWebApplicationFactory also works with a Spring Annotation
approach, but since it returns a SpringWebApplication (deprecated) should
it be avoided?
I would love to hear from the Wicket team as far as the recommended
configuration.
Notice: This communication, including any attachments, is intended solely
for the use of the individual or entity to which it is addressed. This
communication may contain information that is protected from disclosure
under State and/or Federal law. Please notify the sender immediately if
you have received this communication in error and delete this email from
your system. If you are not the intended recipient, you are requested not
to disclose, copy, distribute or take any action in reliance on the
contents of this information.
Re: WicketFilter Config
Posted by Cemal Bayramoglu <jW...@cabouge.com>.
See if http://jweekend.com/dev/LegUp gives you an easy way to get started.
Regards - Cemal
jWeekend
OO & Java Technologies, Wicket
Consulting, Development, Training
http://jWeekend.com
On 25 March 2010 18:22, <MZ...@osc.state.ny.us> wrote:
> Due to the fact that SpringWebApplication is deprecated, we evaluated
> several ways of configuring Wicket using WicketFilter. I found
> ContextParamWebApplicationFactory to work with a Spring Annotation
> approach. SpringWebApplicationFactory also works with a Spring Annotation
> approach, but since it returns a SpringWebApplication (deprecated) should
> it be avoided?
>
> I would love to hear from the Wicket team as far as the recommended
> configuration.
>
>
>
> Notice: This communication, including any attachments, is intended solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketFilter Config
Posted by James Carman <jc...@carmanconsulting.com>.
Well, if you need to configure (i.e. set properties on, etc) your
application object via Spring, then you either need to use
SpringWebApplicationFactory or write your own class that does the same thing
(that's not deprecated).
On Mon, Mar 29, 2010 at 4:36 PM, <MZ...@osc.state.ny.us> wrote:
> Yes we are using Spring. Our Spring configuration works with either the
> SpringWebApplicationFactory or ContextParamWebApplicationFactory.
>
>
>
>
> James Carman <jc...@carmanconsulting.com>
> 03/29/2010 04:31 PM
> Please respond to
> users@wicket.apache.org
>
>
> To
> users@wicket.apache.org
> cc
>
> Subject
> Re: WicketFilter Config
>
>
>
>
>
>
> Do you want/need to configure your application via Spring?
>
> On Mon, Mar 29, 2010 at 4:27 PM, <MZ...@osc.state.ny.us> wrote:
>
> > Igor,
> > We are using WicketFilter with SpringWebApplicationFactory. This works
> > fine, but I've noticed SpringWebApplication has been deprecated, and
> since
> > SpringWebApplicationFactory returns a SpringWebApplication we tried the
> > ContextParamWebApplicationFactory which also works.
> >
> > Which is preferred, since SpringWebApplication is deprecated should we
> > avoid using it by using the ContextParamWebApplicationFactory?
> >
> >
> >
> >
> >
> > Igor Vaynberg <ig...@gmail.com>
> > 03/25/2010 05:03 PM
> > Please respond to
> > users@wicket.apache.org
> >
> >
> > To
> > users@wicket.apache.org
> > cc
> >
> > Subject
> > Re: WicketFilter Config
> >
> >
> >
> >
> >
> >
> > recommended configuration is on our wiki's spring page
> >
> > -igor
> >
> > On Thu, Mar 25, 2010 at 11:22 AM, <MZ...@osc.state.ny.us> wrote:
> > > Due to the fact that SpringWebApplication is deprecated, we evaluated
> > > several ways of configuring Wicket using WicketFilter. I found
> > > ContextParamWebApplicationFactory to work with a Spring Annotation
> > > approach. SpringWebApplicationFactory also works with a Spring
> > Annotation
> > > approach, but since it returns a SpringWebApplication (deprecated)
> > should
> > > it be avoided?
> > >
> > > I would love to hear from the Wicket team as far as the recommended
> > > configuration.
> > >
> > >
> > >
> > > Notice: This communication, including any attachments, is intended
> > solely
> > > for the use of the individual or entity to which it is addressed. This
> > > communication may contain information that is protected from
> disclosure
> > > under State and/or Federal law. Please notify the sender immediately
> if
> > > you have received this communication in error and delete this email
> from
> > > your system. If you are not the intended recipient, you are requested
> > not
> > > to disclose, copy, distribute or take any action in reliance on the
> > > contents of this information.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
> >
> >
> >
> > Notice: This communication, including any attachments, is intended
> solely
> > for the use of the individual or entity to which it is addressed. This
> > communication may contain information that is protected from disclosure
> > under State and/or Federal law. Please notify the sender immediately if
> > you have received this communication in error and delete this email from
> > your system. If you are not the intended recipient, you are requested
> not
> > to disclose, copy, distribute or take any action in reliance on the
> > contents of this information.
> >
>
>
>
>
>
> Notice: This communication, including any attachments, is intended solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
>
Re: WicketFilter Config
Posted by MZ...@osc.state.ny.us.
Yes we are using Spring. Our Spring configuration works with either the
SpringWebApplicationFactory or ContextParamWebApplicationFactory.
James Carman <jc...@carmanconsulting.com>
03/29/2010 04:31 PM
Please respond to
users@wicket.apache.org
To
users@wicket.apache.org
cc
Subject
Re: WicketFilter Config
Do you want/need to configure your application via Spring?
On Mon, Mar 29, 2010 at 4:27 PM, <MZ...@osc.state.ny.us> wrote:
> Igor,
> We are using WicketFilter with SpringWebApplicationFactory. This works
> fine, but I've noticed SpringWebApplication has been deprecated, and
since
> SpringWebApplicationFactory returns a SpringWebApplication we tried the
> ContextParamWebApplicationFactory which also works.
>
> Which is preferred, since SpringWebApplication is deprecated should we
> avoid using it by using the ContextParamWebApplicationFactory?
>
>
>
>
>
> Igor Vaynberg <ig...@gmail.com>
> 03/25/2010 05:03 PM
> Please respond to
> users@wicket.apache.org
>
>
> To
> users@wicket.apache.org
> cc
>
> Subject
> Re: WicketFilter Config
>
>
>
>
>
>
> recommended configuration is on our wiki's spring page
>
> -igor
>
> On Thu, Mar 25, 2010 at 11:22 AM, <MZ...@osc.state.ny.us> wrote:
> > Due to the fact that SpringWebApplication is deprecated, we evaluated
> > several ways of configuring Wicket using WicketFilter. I found
> > ContextParamWebApplicationFactory to work with a Spring Annotation
> > approach. SpringWebApplicationFactory also works with a Spring
> Annotation
> > approach, but since it returns a SpringWebApplication (deprecated)
> should
> > it be avoided?
> >
> > I would love to hear from the Wicket team as far as the recommended
> > configuration.
> >
> >
> >
> > Notice: This communication, including any attachments, is intended
> solely
> > for the use of the individual or entity to which it is addressed. This
> > communication may contain information that is protected from
disclosure
> > under State and/or Federal law. Please notify the sender immediately
if
> > you have received this communication in error and delete this email
from
> > your system. If you are not the intended recipient, you are requested
> not
> > to disclose, copy, distribute or take any action in reliance on the
> > contents of this information.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
>
>
> Notice: This communication, including any attachments, is intended
solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested
not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
>
Notice: This communication, including any attachments, is intended solely
for the use of the individual or entity to which it is addressed. This
communication may contain information that is protected from disclosure
under State and/or Federal law. Please notify the sender immediately if
you have received this communication in error and delete this email from
your system. If you are not the intended recipient, you are requested not
to disclose, copy, distribute or take any action in reliance on the
contents of this information.
Re: WicketFilter Config
Posted by James Carman <jc...@carmanconsulting.com>.
Do you want/need to configure your application via Spring?
On Mon, Mar 29, 2010 at 4:27 PM, <MZ...@osc.state.ny.us> wrote:
> Igor,
> We are using WicketFilter with SpringWebApplicationFactory. This works
> fine, but I've noticed SpringWebApplication has been deprecated, and since
> SpringWebApplicationFactory returns a SpringWebApplication we tried the
> ContextParamWebApplicationFactory which also works.
>
> Which is preferred, since SpringWebApplication is deprecated should we
> avoid using it by using the ContextParamWebApplicationFactory?
>
>
>
>
>
> Igor Vaynberg <ig...@gmail.com>
> 03/25/2010 05:03 PM
> Please respond to
> users@wicket.apache.org
>
>
> To
> users@wicket.apache.org
> cc
>
> Subject
> Re: WicketFilter Config
>
>
>
>
>
>
> recommended configuration is on our wiki's spring page
>
> -igor
>
> On Thu, Mar 25, 2010 at 11:22 AM, <MZ...@osc.state.ny.us> wrote:
> > Due to the fact that SpringWebApplication is deprecated, we evaluated
> > several ways of configuring Wicket using WicketFilter. I found
> > ContextParamWebApplicationFactory to work with a Spring Annotation
> > approach. SpringWebApplicationFactory also works with a Spring
> Annotation
> > approach, but since it returns a SpringWebApplication (deprecated)
> should
> > it be avoided?
> >
> > I would love to hear from the Wicket team as far as the recommended
> > configuration.
> >
> >
> >
> > Notice: This communication, including any attachments, is intended
> solely
> > for the use of the individual or entity to which it is addressed. This
> > communication may contain information that is protected from disclosure
> > under State and/or Federal law. Please notify the sender immediately if
> > you have received this communication in error and delete this email from
> > your system. If you are not the intended recipient, you are requested
> not
> > to disclose, copy, distribute or take any action in reliance on the
> > contents of this information.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
>
>
> Notice: This communication, including any attachments, is intended solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
>
Re: WicketFilter Config
Posted by MZ...@osc.state.ny.us.
Igor,
We are using WicketFilter with SpringWebApplicationFactory. This works
fine, but I've noticed SpringWebApplication has been deprecated, and since
SpringWebApplicationFactory returns a SpringWebApplication we tried the
ContextParamWebApplicationFactory which also works.
Which is preferred, since SpringWebApplication is deprecated should we
avoid using it by using the ContextParamWebApplicationFactory?
Igor Vaynberg <ig...@gmail.com>
03/25/2010 05:03 PM
Please respond to
users@wicket.apache.org
To
users@wicket.apache.org
cc
Subject
Re: WicketFilter Config
recommended configuration is on our wiki's spring page
-igor
On Thu, Mar 25, 2010 at 11:22 AM, <MZ...@osc.state.ny.us> wrote:
> Due to the fact that SpringWebApplication is deprecated, we evaluated
> several ways of configuring Wicket using WicketFilter. I found
> ContextParamWebApplicationFactory to work with a Spring Annotation
> approach. SpringWebApplicationFactory also works with a Spring
Annotation
> approach, but since it returns a SpringWebApplication (deprecated)
should
> it be avoided?
>
> I would love to hear from the Wicket team as far as the recommended
> configuration.
>
>
>
> Notice: This communication, including any attachments, is intended
solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested
not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Notice: This communication, including any attachments, is intended solely
for the use of the individual or entity to which it is addressed. This
communication may contain information that is protected from disclosure
under State and/or Federal law. Please notify the sender immediately if
you have received this communication in error and delete this email from
your system. If you are not the intended recipient, you are requested not
to disclose, copy, distribute or take any action in reliance on the
contents of this information.
Re: WicketFilter Config
Posted by Igor Vaynberg <ig...@gmail.com>.
recommended configuration is on our wiki's spring page
-igor
On Thu, Mar 25, 2010 at 11:22 AM, <MZ...@osc.state.ny.us> wrote:
> Due to the fact that SpringWebApplication is deprecated, we evaluated
> several ways of configuring Wicket using WicketFilter. I found
> ContextParamWebApplicationFactory to work with a Spring Annotation
> approach. SpringWebApplicationFactory also works with a Spring Annotation
> approach, but since it returns a SpringWebApplication (deprecated) should
> it be avoided?
>
> I would love to hear from the Wicket team as far as the recommended
> configuration.
>
>
>
> Notice: This communication, including any attachments, is intended solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org