You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Michael Youngstrom <yo...@gmail.com> on 2007/07/17 22:02:04 UTC
Tomcat 6 sessionDidActivate() being called before contextInitialized()
I'm using Seam and a Seam app depends upon the Seam application being
initialized before you can do much of anything in Seam.
That said Seam puts some hooks into the sessionDidActivate() and
sessionDidPassivate() events. Because of that when I start up my app
I'm getting a Seam IllegalStateException because the
contextInitialized() event is fired after sessionDidActivate() so Seam
is not yet initialized it's Session hooks are being fired.
On a side note I noticed that sessionWillPassivate() is being before
contextDestroyed(). So it would seem that to be consistent
sessionDidActivate() should be called after contextInitialized().
Thoughts?
Should I log a bug?
Here is the related Seam issue: http://jira.jboss.com/jira/browse/JBSEAM-1681
Mike
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 6 sessionDidActivate() being called before contextInitialized()
Posted by Michael Youngstrom <yo...@gmail.com>.
I went ahead and created an issue:
http://issues.apache.org/bugzilla/show_bug.cgi?id=42934
On 7/17/07, Michael Youngstrom <yo...@gmail.com> wrote:
> I'm using Seam and a Seam app depends upon the Seam application being
> initialized before you can do much of anything in Seam.
>
> That said Seam puts some hooks into the sessionDidActivate() and
> sessionDidPassivate() events. Because of that when I start up my app
> I'm getting a Seam IllegalStateException because the
> contextInitialized() event is fired after sessionDidActivate() so Seam
> is not yet initialized it's Session hooks are being fired.
>
> On a side note I noticed that sessionWillPassivate() is being before
> contextDestroyed(). So it would seem that to be consistent
> sessionDidActivate() should be called after contextInitialized().
>
> Thoughts?
>
> Should I log a bug?
>
> Here is the related Seam issue: http://jira.jboss.com/jira/browse/JBSEAM-1681
>
> Mike
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org