Is there any reason why we can't make it so that every message context
has an id when its created? I'm fine with having getId() and setId() so
that the default ID can be changed but it seems to me that we never use
a message context without setting the ID. This avoids repeated code
fragments like:
Hi Sanjiva:
> Is there any reason why we can't make it so that every message context
> has an id when its created? I'm fine with having getId() and setId() so
> that the default ID can be changed but it seems to me that we never use
> a message context without setting the ID. This avoids repeated
While we're on the subject I'd like to comment since I actually use UUID's. I
use them to keep track of users who have logged in. AFAIK
maintainSession(true) doesn't work with multiple services. I'd like to use
ServiceGroupContext and WS-Addressing to do this. Yet it seems harder then it
should
