You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ralf Edmund Stranzenbach (JIRA)" <ta...@jakarta.apache.org> on 2005/07/28 23:35:20 UTC
[jira] Created: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Attribute (persist=client) not rewound on form-submit
-----------------------------------------------------
Key: TAPESTRY-454
URL: http://issues.apache.org/jira/browse/TAPESTRY-454
Project: Tapestry
Type: Bug
Components: Framework
Versions: 4.0
Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
Reporter: Ralf Edmund Stranzenbach
Attachments: Components.zip
My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
This works fine in view mode.
If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
I've checked the components by changing persistence to persist=session and my components worked as expected.
I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Assigned: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-454?page=all ]
Howard M. Lewis Ship reassigned TAPESTRY-454:
---------------------------------------------
Assign To: Howard M. Lewis Ship
> Attribute (persist=client) not rewound on form-submit
> -----------------------------------------------------
>
> Key: TAPESTRY-454
> URL: http://issues.apache.org/jira/browse/TAPESTRY-454
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
> Reporter: Ralf Edmund Stranzenbach
> Assignee: Howard M. Lewis Ship
> Attachments: Components.zip, sample.html
>
> My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
> An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
> This works fine in view mode.
> If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
> Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
> I've checked the components by changing persistence to persist=session and my components worked as expected.
> I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Resolved: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-454?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-454:
-------------------------------------------
Resolution: Cannot Reproduce
I put together a quick scratch page and determined that it works fine (at least in beta-4). Not sure what the issue was, but there have been some bug fixes related to transient properties and others related to DataSqueezer, and that may account for it.
> Attribute (persist=client) not rewound on form-submit
> -----------------------------------------------------
>
> Key: TAPESTRY-454
> URL: http://issues.apache.org/jira/browse/TAPESTRY-454
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
> Reporter: Ralf Edmund Stranzenbach
> Assignee: Howard M. Lewis Ship
> Attachments: Components.zip, sample.html
>
> My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
> An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
> This works fine in view mode.
> If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
> Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
> I've checked the components by changing persistence to persist=session and my components worked as expected.
> I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Posted by "Ralf Edmund Stranzenbach (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-454?page=comments#action_12318726 ]
Ralf Edmund Stranzenbach commented on TAPESTRY-454:
---------------------------------------------------
Whatever reason it has been - starting with Tapestry 4.0-beta4 it seems to work without any problems.
> Attribute (persist=client) not rewound on form-submit
> -----------------------------------------------------
>
> Key: TAPESTRY-454
> URL: http://issues.apache.org/jira/browse/TAPESTRY-454
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
> Reporter: Ralf Edmund Stranzenbach
> Attachments: Components.zip, sample.html
>
> My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
> An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
> This works fine in view mode.
> If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
> Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
> I've checked the components by changing persistence to persist=session and my components worked as expected.
> I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-454?page=comments#action_12317700 ]
Howard M. Lewis Ship commented on TAPESTRY-454:
-----------------------------------------------
I can't think, off the top of my head, of any reason it would behave the way you say. I'm not doubting you ... but I'm concerned there's something else going on, such as that old bugaboo -- page caching (on the client, or on some intermediate server).
What I'd love to see would be the rendered OUTPUT of the page; that way, we could verify that the state was encoded into the form; that's the first step towards ensuring that the state is restored when the form is submitted.
> Attribute (persist=client) not rewound on form-submit
> -----------------------------------------------------
>
> Key: TAPESTRY-454
> URL: http://issues.apache.org/jira/browse/TAPESTRY-454
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
> Reporter: Ralf Edmund Stranzenbach
> Attachments: Components.zip
>
> My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
> An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
> This works fine in view mode.
> If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
> Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
> I've checked the components by changing persistence to persist=session and my components worked as expected.
> I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Posted by "Ralf Edmund Stranzenbach (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-454?page=all ]
Ralf Edmund Stranzenbach updated TAPESTRY-454:
----------------------------------------------
Attachment: Components.zip
Source of ActorPage and View component that raise the specific error situation.
> Attribute (persist=client) not rewound on form-submit
> -----------------------------------------------------
>
> Key: TAPESTRY-454
> URL: http://issues.apache.org/jira/browse/TAPESTRY-454
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
> Reporter: Ralf Edmund Stranzenbach
> Attachments: Components.zip
>
> My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
> An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
> This works fine in view mode.
> If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
> Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
> I've checked the components by changing persistence to persist=session and my components worked as expected.
> I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-454) Attribute (persist=client) not rewound on form-submit
Posted by "Ralf Edmund Stranzenbach (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-454?page=all ]
Ralf Edmund Stranzenbach updated TAPESTRY-454:
----------------------------------------------
Attachment: sample.html
This is a snapshot of the applications output in the situation where an submit to the bottom form will result in an false rewind on the actorId parameter.
> Attribute (persist=client) not rewound on form-submit
> -----------------------------------------------------
>
> Key: TAPESTRY-454
> URL: http://issues.apache.org/jira/browse/TAPESTRY-454
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Environment: Tapestry 4.0-beta3, Tomcat 5.0.28, JDK 1.4.2_08, Windows-XP
> Reporter: Ralf Edmund Stranzenbach
> Attachments: Components.zip, sample.html
>
> My application uses a page (ActorPage) as the main page for actor/user management. To keep the focus on the actual selected Actor instance, this page contains an attribute named ActorId which stores the selected actors id. This attribute is declared as both persist=client or persist=client:page.
> An additional View component should display additional information on the selected actor and allows modification to it's attributes. To gain access to the actor, this component references the actorId as a parameter.
> This works fine in view mode.
> If a submit action takes place on the Views form component, during the execution of the form's listener, the actorId parameter returns a false value.
> Based on my experiences, it is all times the first value assigned to the actorId during this session. So i guess, it is not rewound correctly and may still contain some old data.
> I've checked the components by changing persistence to persist=session and my components worked as expected.
> I'll attach some excerpt of the applications code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org