[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2105) pluggable conversation id strategy
[ http://jira.jboss.com/jira/browse/JBSEAM-2105?page=comments#action_12383113 ]
Norman Richards commented on JBSEAM-2105:
-----------------------------------------
Sorry - I misread your previous statement. I thought you were suggesting moving
per-session unique ids (which I thought was our current implementation to application-wide
unique ids. I had to check, because I really thought we currently had per-session ids,
but id generation is application-wide and reset at redeploy. (and has been for quite some
time, as far as I can tell) That only strengthens the argument that some deployments may
want a different id generation strategy.
pluggable conversation id strategy
----------------------------------
Key: JBSEAM-2105
URL: http://jira.jboss.com/jira/browse/JBSEAM-2105
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Norman Richards
Fix For: 2.0.1.GA
Attachments: patch_file
Conversation id generation should be managed by a component that can be overridden for
specific deployments. We might even consider providing a more interesting default (or
optional) strategy like a GUID.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira