Issue 348 in emite: Use of SessionStates.ready.equals(state) problems

1 view
Skip to first unread message

em...@googlecode.com

unread,
Feb 20, 2011, 8:03:56 PM2/20/11
to emit...@googlegroups.com
Status: Accepted
Owner: vruiz.ju...@gmail.com
Labels: Type-Defect Priority-Medium

New issue 348 by vruiz.ju...@gmail.com: Use of
SessionStates.ready.equals(state) problems
http://code.google.com/p/emite/issues/detail?id=348

The use of:
SessionStates.ready.equals(state) or SessionStates.isReady
gives wrongs values when you are at "Ready" state and you goes to
the "RosterReady" state (for instance).

As a result instead of be logged, Hablar seems disconnected, your roster is
inactive and Login Page shows "Wait..." instead of the Logout button.

How to test it: Active the LoginPage and try to login/logout several times.
You will see that you can login only one time (when the browser load
Hablar).

How to fix it: Use session.isReady() (in XmppSession) instead of
SessionStates.ready.equals(state), or fix SessionState.isReady.

em...@googlecode.com

unread,
Feb 24, 2011, 10:12:38 AM2/24/11
to emit...@googlegroups.com
Updates:
Labels: Milestone-Release1.0

Comment #1 on issue 348 by ashward....@gmail.com: Use of
SessionStates.ready.equals(state) problems
http://code.google.com/p/emite/issues/detail?id=348

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages