On Wed, 29 Jun 2011 15:20:48 -0300, Josh Canfield
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 same thing in a Tapestr
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, Tim
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 c
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 scratchi
On Wed, 11 May 2011 15:35:15 -0300, Tim Koop 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 (like Google) to
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 m
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" :
On Wed, 11 May 2011 15:17:42 -0300, Tim Koop 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 page where it get
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 is
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 SSO,
On Wed, 11 May 2011 14:01:01 -0300, Tim Koop wrote:
I'm having a little problem with even a simple SessionState String
object.
Try @SessionState(create = false). Better yet, create a class to represent
your user session state and put this userColour field there, as a
@SessionState object
11 matches
Mail list logo
