struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Patrick (JIRA)" <>
Subject [jira] [Commented] (WW-4190) Struts Tag Form & URL explicit excludeSession attribute
Date Fri, 06 Sep 2013 09:28:52 GMT


John Patrick commented on WW-4190:

I'm totally aware about Session Management, the bit I was unclear about was how Struts2 handled
it. From your comments it sounds like Struts2 totally delegate the responsibility to the container
to handle url generate.

As you have both stated, and now you have made me aware of this delegation I also agree any
update to Struts2 would be a hack/fudge and would need to post process the url returned from
the container and remove the session details.

So the best solution would for the next web container spec to have this support, then StrutsX
would simply need to be update so this option could be passed through.
> Struts Tag Form & URL explicit excludeSession attribute
> -------------------------------------------------------
>                 Key: WW-4190
>                 URL:
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Plugin - Tags
>    Affects Versions:
>         Environment: N/A
>            Reporter: John Patrick
>            Priority: Minor
> Can an addition attribute be added to both the :form and :url tags to explicitly include
or exclude the session details. Leave default behavior as before, but if excludeSession="true"
then JSESSIONID or what ever session variable name is used, then explicitly don't put the
session details on the URL generated.
> I've worked on a few projects that have had to process the URL before using as we have
needed to explicitly not include the session details.
> I'll start thinking about patch etc, but someone up to speed with struts it might only
be a 5 or 15 min job for them.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message