-
1. Re: Seam on JBossESB
burrsutter Feb 19, 2007 9:17 PM (in response to burrsutter)Seam also needs us (ESB) to handle some form of context identifier between service invocations. Think of this as a cookie for a typical web-based application.
The use of a Message header/property could do the trick but the interface method signature I proposed earlier doesn't address this requirement. -
2. Re: Seam on JBossESB
marklittle Feb 20, 2007 4:56 AM (in response to burrsutter)Do you mean a session identifier?
-
3. Re: Seam on JBossESB
tfennelly Feb 20, 2007 5:15 AM (in response to burrsutter)"mark.little@jboss.com" wrote:
Do you mean a session identifier?
I'd suspect that it could be more than a session-id. Seam supports the notion of at "conversation context", which exists within the context of a session. You can have multiple conversations running in parallel within a single session. It tracks this using a conversation-id. So, I'd suspect they need something that they can map to something like "session-id:conversation-id". Not sure what Gavin/Burr has in mind - perhaps they've no intention of supporting anything beyond an equivalent of a session-id. -
4. Re: Seam on JBossESB
marklittle Feb 20, 2007 5:18 AM (in response to burrsutter)Context is the best place for this information. Not sure at the moment whether that is a 4.2 or a 5.0 item though. If not 4.2 then we can fudge it in WS-A, but that leads to backward compatibility problems when we eventually do it right. Anyway, I'll wait to hear from Burr.
-
5. Re: Seam on JBossESB
burrsutter Feb 20, 2007 7:49 AM (in response to burrsutter)We (Gavin and I) didn't discuss the distinction between having a conversational context id vs a session id. I'm guessing that it is more a session id and he manages the "conversation" on his side of things.
I've sent him a link to this thread to see if he'll comment.