[#BLZ-190] LoginManager.start/stop should call LoginCommand.start/stop.

BlazeDS

Created: 06/02/08 02:59 PM Updated: 05/27/09 01:13 PM

Component/s:

Security

Security Level:

Public (All JIRA Users )

Severity:	Non Functioning
Reproducibility:	Every Time
Discoverability:	Medium
Found in Version:	BlazeDS 3.0.1
Milestone:	BlazeDS 4 Beta 2
Affected OS(s):	All OS Platforms - All
Steps to Reproduce:	« Hide LoginCommand defines start and stop methods but these methods are not called by the BlazeDS code. This is problematic if someone wants to implement a custom LoginCommand, as they cannot control LoginCommand's creation/deletion steps. LoginCommand is managed by LoginManager so LoginManager.start/stop should call LoginCommand.start/stop. Show » LoginCommand defines start and stop methods but these methods are not called by the BlazeDS code. This is problematic if someone wants to implement a custom LoginCommand, as they cannot control LoginCommand's creation/deletion steps. LoginCommand is managed by LoginManager so LoginManager.start/stop should call LoginCommand.start/stop.
Language Found:	English
Bugbase Id:	none
Triaged:	No
Regression:	No
QA Owner:	Kumaran Nallore
Resolved by:	Mete Atamel
Participants:	John Zhao and Mete Atamel
JDK:	Sun JDK 5
Application Server:	Apache Tomcat 6.x

All

Comments

Sort Order:

[ Permlink | « Hide ]

Fixed with change 7223 in BlazeDS trunk.

[ Permlink | « Hide ]

Assign to Kumaran for verification.

[ Permlink | « Hide ]

Confirm the fix and close the bug.