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=24545>. 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=24545 DataSourceRealm cannot see JNDI DataSource defined within a Context ------- Additional Comments From [EMAIL PROTECTED] 2003-11-10 07:17 ------- That's precisely the problem: DataSourceRealm does *not* see any Container DataSources: it only sees ones defined as global resources. It seems logical that if I define a "jdbc/UserDB" DataSource in a Host, the Realm defined in that Host or any Container underneath it should see that JNDI-exposed resource. I think the assertion that a Realm isn't usually defined in a Context is erronious. I do it. And it's useful to define a Realm on a per-context basis, allowing you to run applications with wildly divergent authentication requirements under a single Tomcat instance. And allowing Realm under a Context (as Tomcat currently does) makes deployment of a turn-key application easier: just drop the Context XML fragment in the webapps directory and be done, no meddling in the server.xml. This sort of modularity is very desireable. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
