+1 for a UUID. Random does not guarantee that the id will be unique at the time 
it is generated so there is a chance for a collision. A UUID on the other hand 
alleviates that concern. 

Currently for monitoring purposes from an interceptor I use a UUID that I 
outject from conversation startup so that I can uniquely identify what sessions 
& principals are on my applications as well as what the state of their 
conversation / biz proc (outcomes exceptions etc...). 

Basically a self rolled admin console results. Not necessary in a regular web 
app but in a DOD Logistical system a requirement.

Just my 2 cents.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095044#4095044

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095044
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to