Bugs item #962365, was opened at 2004-05-28 10:54
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=962365&group_id=22866

Category: JBossSX
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Brian Topping (topping)
>Assigned to: Scott M Stark (starksm)
Summary: dsJndiName should have protected access in DB LoginModule

Initial Comment:
Revision 1.6.4.1 of 
org.jboss.security.auth.spi.DatabaseServerLoginModule.ja
va line 55 has private class field dsJndiName.  This field 
(and potentially all of the fields of this class) need to 
have protected access so subclasses can have read 
access to them.  

The local need for this is that a client is has a sub-
optimal roles mapping database structure, and it would 
be easiest to subclass the DatabaseServerLoginModule, 
simply overriding getRoleSets until they can migrate to a 
better system.

----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2004-06-19 21:32

Message:
Logged In: YES 
user_id=175228

This was changed in 3.2.4

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=962365&group_id=22866


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to