Bugs item #962365, was opened at 2004-05-28 13:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=962365&group_id=22866
Category: JBossSX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Brian Topping (topping) Assigned to: Nobody/Anonymous (nobody) 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. ---------------------------------------------------------------------- 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: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
