Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 54791 invoked from network); 12 Jun 2003 14:31:55 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 12 Jun 2003 14:31:55 -0000 Received: (qmail 19937 invoked by uid 97); 12 Jun 2003 14:34:13 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 19930 invoked from network); 12 Jun 2003 14:34:12 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 12 Jun 2003 14:34:12 -0000 Received: (qmail 52853 invoked by uid 500); 12 Jun 2003 14:31:24 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 52814 invoked from network); 12 Jun 2003 14:31:24 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 12 Jun 2003 14:31:24 -0000 Received: (qmail 19914 invoked by uid 50); 12 Jun 2003 14:33:42 -0000 Date: 12 Jun 2003 14:33:42 -0000 Message-ID: <20030612143342.19913.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 16316] - DataSourceRealm can not find JNDI name in context X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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 unico@hippo.nl 2003-06-12 14:33 ------- I also have to object to the dismissal of this issue. I understand the logic that a Realm can have wider scope (Host, Container) and therefore should not depend on an object of more narrow scope (Context) in those cases. But this does not mean that once a Realm is defined inside Context scope it shouldn't be allowed to access an object inside that same scope. I simply do not wish to expose that datasource to any other application than the one I need it for, and so I need to be able to define it inside the application Context. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org