Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 2.1.1
-
Fix Version/s: Bug Backlog
-
Component/s: Core: Sessions
-
Labels:None
-
User impact:Low
-
Similar Issues:None
Description
Right now if you want to get to a session property you have to go to the event to get the session. I think this is fine except there is a session scope on the MessagePRopertiesContext that can be used to set a Session property via the message, which also seems reasonable. Anyone have any thoughts on this?
Issue Links
- duplicates
-
MULE-4431
Session scoped properties get lost
-
I'm all for this. With the fix for
MULE-4117, this should work just fine now.MULE-4117, this should work just fine now.