Success I think. My brain is totally fired at this point, so if someone
can see the problem in this, bellow loudly please!
The Channel set I've authenticated has two MessageAgents attached, one
of which is an AuthenticationAgent. I call connect on the second
Channelset with the AuthenticationAg
Rolling back to BlazeDS 3.0.0.544 gets rid of the duplicate session
issue, but the second session is still not authenticated, again because
it's trying to use a different JSessionId.
So it boils down to Flash side of things, what can I do to set the
JSessionId from one Channel on another?
With further reading it appears that having two Channels going to the
same server isn't allowed by BlazeDS anyway! It will throw errors around
DuplicateSessions, because the JsessionId isn't shared between the
channels.
It surely can't be this hard to do something so straightforward?
It also appears BlazeDS doesn't agree with the Flex documentation...
Channelset says the RO is authenticated if one of the channels in the
set is.
I set up two ROs, and two Channelsets each with the same two Channels
but in a different order (secure first in one, non-secure in the other),
then
4 matches
Mail list logo
