tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (TAP5-408) Inside Form.java, any changes to tracker need to call setTracker, to update session object properly
Date Tue, 30 Dec 2008 17:39:44 GMT

     [ https://issues.apache.org/jira/browse/TAP5-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship reassigned TAP5-408:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Inside Form.java, any changes to tracker need to call setTracker, to update session object
properly
> ---------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-408
>                 URL: https://issues.apache.org/jira/browse/TAP5-408
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0, 5.1, 5.0.15, 5.0.16, 5.0.17, 5.0.18
>            Reporter: Fernando
>            Assignee: Howard M. Lewis Ship
>            Priority: Critical
>         Attachments: form-session.diff
>
>
> I talked about this on the mailing list.  HttpSession objects have a requirement that
if you dirty an object assigned to it, you have to call setAttribute again, to tell the app
server the object has been modified.
> Most of the code within Form.java does this properly ( whenever the tracker is modified,
it calls setTracker, or _tracker = tracker, etc ).
> It missed one spot, and this is a very small patch to fix it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message