tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16316] - DataSourceRealm can not find JNDI name in context
Date Thu, 12 Jun 2003 13:27:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16316>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16316

DataSourceRealm can not find JNDI name in context





------- Additional Comments From dan@mojavelinux.com  2003-06-12 13:27 -------
I don't understand this WONTFIX status.  You mean to tell me that two people
running webapps on the same server can't use different databases for container
managed security?  Suppost Joe is running a shopping cart and I have a weblog. 
That doesn't mean we have the same users and therefore doesn't mean we should
use the same JNDI to get a database connection.  If you use the JDBCRealm you
can specify all the parameters you want for container managed security, why
can't you use an JNDI too?  This makes no sense to me.

p.s. How did I get it to run?  Check out securityfilter.sourceforge.net, which
allows pseudo-container managed security so the specification for the realm can
be anywhere.  securityfilter get's over some of the pitfalls of container
managed security such as not being able to have a login on any page.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message