You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/05/22 12:18:28 UTC
DO NOT REPLY [Bug 39630] New: - Context creation fails when the context tries to bind to an unknown JNDI resource
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39630>.
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
DO NOT REPLY [Bug 39630] - Context creation fails when the context tries to bind to an unknown JNDI resource
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39630>.
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
yoavs@computer.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From yoavs@computer.org 2006-12-24 19:35 -------
Lee, I see your use-case and I understand your problem. I'm changing this to an
enhancement request accordingly.
Just FYI, the Tomcat admin webapp is receiving fairly little love (i.e. active
work for improvement) these days. The chances of getting this done are much
higher if you submit a patch we can evaluate and commit, rather than wait for us
to do this ourselves based on your request.
--
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