Menu

#49 ConnectionBean - DisableHeader problem 2

jabberbeans_backend
open
nobody
None
5
2013-02-19
2002-03-05
Anonymous
No

Hi,

I've found whe the handshake failed in the
serverside.Launcher class.

When using DisableAutoHeader, no XMLStreamMonitor is
created, so the sessionID of the ConnectionBean is not
set.

The launcher synchronizes on the reception of a stream
packet, and then calls ConnectionBean.getSessionID(),
which returns null.

Then, the SHA1 digest is calculated on a null
sessionID, and returns a wrong value...

I didn't find any elegant and simple solution to this
problem. The better solution would be to modify
the "connect" methods and add a parameter.
Something like "int ConnectionMode" and define some
static fields : CLIENT, COMPONENT_CONNECT,
COMPONENT_ACCEPT, COMPONENT_EXEC.
This would suppress the need of the "DisableAutoHeader
function" :-)

Discussion


Log in to post a comment.