myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathias Werlitz (JIRA)" <>
Subject [jira] Commented: (MYFACES-616) tree2 creates TWO cookies
Date Sat, 24 Sep 2005 00:16:28 GMT
    [ ] 

Mathias Werlitz commented on MYFACES-616:

getting rid of cookies would breake the preserveToggle feature in client side toggle mode

> tree2 creates TWO cookies
> -------------------------
>          Key: MYFACES-616
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: Tomahawk
>     Versions: Nightly Build
>     Reporter: Jan Dockx

> Cookies for tree2 are generated by JavaScript, with as name the (simple) JSF id of the
tree2 component, and as path the "current URL directory". However, in a normal JSF-to-JSF
navigation, the first time the tree is rendered, we came from another page, and the URL is
the URL of that previous page (in JSF, the URL is always 1 step behind). When we have server
interaction within the page the tree is on, after the first interaction, the URL is changed
to the URL of the second page, and a second cookie is created for that "URL directory". This
is not an issue in itself if both pages are in the same directory, but becomes apparent if
they are not.
> This is probably hard to fix when looked at narrowly, because of the "URL is always 1
step behind" JSF issue. The real issue is, however, that the path of the cookie should be
the webapp context, like JSESSIONID has, and not the "current URL directory". The viewId could
then be made part of the cookie name, to make it unique.
> (Or, for an even more bold suggestion: we should get writ of the cookies, and store the
state in a hidden field. Cookies can be used for storing state across requests, but for tree2
that is exactly what we don't want: we want to get the info to the server, let the server
define a new state, and then get that back.)

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

View raw message