Re: Session.attach
> > Added: https://issues.apache.org/jira/browse/WICKET-3125 > And now completed (for 1.5-M3) -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
Re: Session.attach
On Wed, Oct 20, 2010 at 4:39 PM, Igor Vaynberg wrote:
> we started doing that in 1.5. egg see
> RequestCycle#register(detachCallback). add an rfe for something like
> irequestlistener { onbegin()/onend()}
>
> -igor
>
> On Wed, Oct 20, 2010 at 2:31 PM, James Carman
> wrote:
> > Is there any chance, since we can break the API a bit, that we can try
> > to introduce a more "listenery" method for stuff like this, rather
> > than overriding methods? Developing frameworks for Wicket is
> > difficult because in order to use these "hooks" you have to have your
> > custom code installed (such as a request cycle, session, etc.). What
> > if other frameworks want to do the same thing? They can't live in the
> > same webapp. It would be great if we could just register a listener
> > for these kinds of things.
> >
>
Added: https://issues.apache.org/jira/browse/WICKET-3125
James / Igor: any other
places you can think of off the top of your head where this pattern would be
useful?
--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket? Use Brix! http://brixcms.org*
Re: Session.attach
we started doing that in 1.5. egg see
RequestCycle#register(detachCallback). add an rfe for something like
irequestlistener { onbegin()/onend()}
-igor
On Wed, Oct 20, 2010 at 2:31 PM, James Carman
wrote:
> Is there any chance, since we can break the API a bit, that we can try
> to introduce a more "listenery" method for stuff like this, rather
> than overriding methods? Developing frameworks for Wicket is
> difficult because in order to use these "hooks" you have to have your
> custom code installed (such as a request cycle, session, etc.). What
> if other frameworks want to do the same thing? They can't live in the
> same webapp. It would be great if we could just register a listener
> for these kinds of things.
>
> On Wed, Oct 20, 2010 at 2:45 PM, Jeremy Thomerson
> wrote:
>> On Wed, Oct 20, 2010 at 1:44 PM, jowen.gsb wrote:
>>
>>>
>>> Since Session.attach() is deprecated, where would the best place be to put
>>> code instead? The current use case is to check that a user has not been
>>> deleted/disabled between request cycles.
>>>
>>> /**
>>> * Any attach logic for session subclasses. Called when a session is
>>> set
>>> for the thread.
>>> *
>>> * @deprecated will not be available in 1.5+
>>> */
>>> �...@deprecated
>>> protected void attach()
>>> {
>>> }
>>>
>>> --
>>> View this message in context:
>>> http://apache-wicket.1842946.n4.nabble.com/Session-attach-tp3004389p3004389.html
>>> Sent from the Users forum 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
>>>
>>>
>> RequestCycle#onBeginRequest?
>>
>> --
>> Jeremy Thomerson
>> http://wickettraining.com
>> *Need a CMS for Wicket? Use Brix! http://brixcms.org*
>>
>
> -
> 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
Re: Session.attach
Is there any chance, since we can break the API a bit, that we can try
to introduce a more "listenery" method for stuff like this, rather
than overriding methods? Developing frameworks for Wicket is
difficult because in order to use these "hooks" you have to have your
custom code installed (such as a request cycle, session, etc.). What
if other frameworks want to do the same thing? They can't live in the
same webapp. It would be great if we could just register a listener
for these kinds of things.
On Wed, Oct 20, 2010 at 2:45 PM, Jeremy Thomerson
wrote:
> On Wed, Oct 20, 2010 at 1:44 PM, jowen.gsb wrote:
>
>>
>> Since Session.attach() is deprecated, where would the best place be to put
>> code instead? The current use case is to check that a user has not been
>> deleted/disabled between request cycles.
>>
>> /**
>> * Any attach logic for session subclasses. Called when a session is
>> set
>> for the thread.
>> *
>> * @deprecated will not be available in 1.5+
>> */
>> �...@deprecated
>> protected void attach()
>> {
>> }
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/Session-attach-tp3004389p3004389.html
>> Sent from the Users forum 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
>>
>>
> RequestCycle#onBeginRequest?
>
> --
> Jeremy Thomerson
> http://wickettraining.com
> *Need a CMS for Wicket? Use Brix! http://brixcms.org*
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Session.attach
On Wed, Oct 20, 2010 at 1:44 PM, jowen.gsb wrote:
>
> Since Session.attach() is deprecated, where would the best place be to put
> code instead? The current use case is to check that a user has not been
> deleted/disabled between request cycles.
>
>/**
> * Any attach logic for session subclasses. Called when a session is
> set
> for the thread.
> *
> * @deprecated will not be available in 1.5+
> */
>@Deprecated
>protected void attach()
>{
>}
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Session-attach-tp3004389p3004389.html
> Sent from the Users forum 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
>
>
RequestCycle#onBeginRequest?
--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket? Use Brix! http://brixcms.org*
Session.attach
Since Session.attach() is deprecated, where would the best place be to put
code instead? The current use case is to check that a user has not been
deleted/disabled between request cycles.
/**
* Any attach logic for session subclasses. Called when a session is set
for the thread.
*
* @deprecated will not be available in 1.5+
*/
@Deprecated
protected void attach()
{
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-attach-tp3004389p3004389.html
Sent from the Users forum 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
