Re: SessionState problems with a String type

2011-06-29 Thread Tim Koop
I'm replying to this somewhat old thread just to say that I have found the problem. The problem was that I had stored something as a SessionState Object (SSO), then I forwarded the user to another website to do some authentication which forwarded the user back to my site. But when the user

Re: SessionState problems with a String type

2011-06-29 Thread Josh Canfield
Ha! Good catch, and annoying. For anyone who hasn't addressed this, when I'm in apache fronted tomcat I use a rewrite rule in apache to make sure everything goes to the www. url... I suppose you could also do the same thing in a Tapestry request filter. Josh On Wed, Jun 29, 2011 at 9:35 AM,

Re: SessionState problems with a String type

2011-06-29 Thread Thiago H. de Paula Figueiredo
On Wed, 29 Jun 2011 15:20:48 -0300, Josh Canfield joshcanfi...@gmail.com wrote: Ha! Good catch, and annoying. For anyone who hasn't addressed this, when I'm in apache fronted tomcat I use a rewrite rule in apache to make sure everything goes to the www. url... I suppose you could also do the

Re: SessionState problems with a String type

2011-05-11 Thread Josh Canfield
http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/annotations/SessionState.html Specifically: public abstract boolean create If true (the default), then referencing an field marked with the annotation will create the SSO. If false, then accessing the field will not create the

Re: SessionState problems with a String type

2011-05-11 Thread Tim Koop
Thanks Josh (and Thiago). I added (create = false), and this certainly got rid of the error message. However, my session object is still either not getting set correctly (even though I clearly visit the page where it gets set, and I even write a message to the log saying I was there), or it

Re: SessionState problems with a String type

2011-05-11 Thread Thiago H. de Paula Figueiredo
On Wed, 11 May 2011 15:17:42 -0300, Tim Koop t...@timkoop.com wrote: Thanks Josh (and Thiago). You're welcome! I added (create = false), and this certainly got rid of the error message. However, my session object is still either not getting set correctly (even though I clearly visit the

Re: SessionState problems with a String type

2011-05-11 Thread Josh Canfield
Are you sure you're getting the same session when you come back to the page? try dumping the session id. @Inject private HttpServletRequest request; void onActivate() { final HttpSession session = request.getSession(false); log.debug(session == null ? Null session :

Re: SessionState problems with a String type

2011-05-11 Thread Tim Koop
I'm trying to authenticate on my website with OpenID, using Java code from the openid4java library. After the user specifies his OpenID provider, the server (Tapestry) is supposed to forward him to the appropriate web page (like Google) to get authenticated, then it forwards the user back to

Re: SessionState problems with a String type

2011-05-11 Thread Thiago H. de Paula Figueiredo
On Wed, 11 May 2011 15:35:15 -0300, Tim Koop t...@timkoop.com wrote: I'm trying to authenticate on my website with OpenID, using Java code from the openid4java library. After the user specifies his OpenID provider, the server (Tapestry) is supposed to forward him to the appropriate web page

Re: SessionState problems with a String type

2011-05-11 Thread Tim Koop
Well, I just tried checking the session id like this, and it is in fact the same after coming back. And the SessionState objects started working too! So then I took out this session id code, and the SessionState objects are still working. So now it's all working fine, and I am left