[jira] [Commented] (TAP5-455) Allow discarding of persistent field changes for specific strategy only

2011-08-12 Thread Massimo Lusetti (JIRA)

[ 
https://issues.apache.org/jira/browse/TAP5-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084103#comment-13084103
 ] 

Massimo Lusetti commented on TAP5-455:
--

Kalle does this still applicable ?

 Allow discarding of persistent field changes for specific strategy only
 ---

 Key: TAP5-455
 URL: https://issues.apache.org/jira/browse/TAP5-455
 Project: Tapestry 5
  Issue Type: Improvement
  Components: tapestry-core
Affects Versions: 5.0.18
Reporter: Kalle Korhonen
Priority: Minor

 Discarding persistent field changes for specific strategies only would be 
 useful for conversational persistent strategies. Currently 
 PersistentFieldManager always iterates over all strategies when 
 discardChanges() is called. Adding discardChanges(String
 strategyName, String pageName) operation to PersistentFieldManager would be 
 enough. See more discussion at 
 http://n2.nabble.com/Discard-persistent-field-changes-for-one-strategy-only--td2179942.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TAP5-455) Allow discarding of persistent field changes for specific strategy only

2011-08-12 Thread Kalle Korhonen (JIRA)

[ 
https://issues.apache.org/jira/browse/TAP5-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084155#comment-13084155
 ] 

Kalle Korhonen commented on TAP5-455:
-

Yes, I'm gonna take this, it's an easy addition.

 Allow discarding of persistent field changes for specific strategy only
 ---

 Key: TAP5-455
 URL: https://issues.apache.org/jira/browse/TAP5-455
 Project: Tapestry 5
  Issue Type: Improvement
  Components: tapestry-core
Affects Versions: 5.0.18
Reporter: Kalle Korhonen
Assignee: Kalle Korhonen
Priority: Minor

 Discarding persistent field changes for specific strategies only would be 
 useful for conversational persistent strategies. Currently 
 PersistentFieldManager always iterates over all strategies when 
 discardChanges() is called. Adding discardChanges(String
 strategyName, String pageName) operation to PersistentFieldManager would be 
 enough. See more discussion at 
 http://n2.nabble.com/Discard-persistent-field-changes-for-one-strategy-only--td2179942.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira