Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 34854 invoked from network); 22 May 2006 10:19:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 May 2006 10:19:14 -0000 Received: (qmail 40791 invoked by uid 500); 22 May 2006 10:19:07 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 40555 invoked by uid 500); 22 May 2006 10:19:06 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 40544 invoked by uid 500); 22 May 2006 10:19:06 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 40538 invoked by uid 99); 22 May 2006 10:19:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 03:19:06 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 03:19:05 -0700 Received: by brutus.apache.org (Postfix, from userid 33) id D16CE714204; Mon, 22 May 2006 10:18:28 +0000 (GMT) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 39630] New: - Context creation fails when the context tries to bind to an unknown JNDI resource Message-ID: X-Bugzilla-Reason: AssignedTo Date: Mon, 22 May 2006 10:18:28 +0000 (GMT) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.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://issues.apache.org/bugzilla/show_bug.cgi?id=39630 Summary: Context creation fails when the context tries to bind to an unknown JNDI resource Product: Tomcat 5 Version: Unknown Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Webapps:Administration AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: lee.mallabone@transactgroup.net This is tested against tomcat version 5.5.17, using the administration webapp. When I create a new Context item, the item is not saved if my webapp tries to access an unbound JNDI resource on startup. The error message displayed is: ------- Warning! Document base does not exist or is not a readable directory Save failed! ------- However, this is untrue - I can see from the console output that tomcat found the webapp but is not catching a javax.naming.NameNotFoundException. Because this happens during the creation of the Tomcat context, there is no way for me to subsequently create the relevant ResourceLinks using the admin webapp. Ideally, the admin webapp would save the context definition so I could then add the relevant JNDI entries to it to make my webapp start up correctly. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org