You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Zarko Lozanoski (JIRA)" <ji...@apache.org> on 2009/10/30 22:19:50 UTC
[jira] Created: (WW-3310) s:select tag to support key as tupple
(Number, Number)
s:select tag to support key as tupple (Number, Number)
------------------------------------------------------
Key: WW-3310
URL: https://issues.apache.org/struts/browse/WW-3310
Project: Struts 2
Issue Type: Improvement
Components: Core Actions
Affects Versions: Future
Reporter: Zarko Lozanoski
Priority: Minor
Currently s:select tag has a nice feature that a Long key can be used - possibly in combination with a persistence provider like hibernate.
When optimistic locking strategy is used, this Long key value does not uniquely identify the entity to be selected, because that entity can be changed by another transaction during the user think time (application session). If a version is added to the key, that will solve the optimistic locking problem nicely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-3310) s:select tag to support key as tupple
(Number, Number)
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47005#action_47005 ]
Musachy Barroso commented on WW-3310:
-------------------------------------
I don't understand the problem. You can use anything for the key. Struts can't know anything about hibernate.
> s:select tag to support key as tupple (Number, Number)
> ------------------------------------------------------
>
> Key: WW-3310
> URL: https://issues.apache.org/struts/browse/WW-3310
> Project: Struts 2
> Issue Type: Improvement
> Components: Core Actions
> Affects Versions: Future
> Reporter: Zarko Lozanoski
> Priority: Minor
>
> Currently s:select tag has a nice feature that a Long key can be used - possibly in combination with a persistence provider like hibernate.
> When optimistic locking strategy is used, this Long key value does not uniquely identify the entity to be selected, because that entity can be changed by another transaction during the user think time (application session). If a version is added to the key, that will solve the optimistic locking problem nicely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.