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=22677>. 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=22677 JNDI not working in Default Context [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2003-11-21 13:30 ------- With regards to the "solution" from Jarkko S, this is defining the JNDI datasource in the specific context, which as mentioned in the original bug report works fine (but is a right pain in the ass because it breaks autodeploy and the JNDI definition gets deleted when you redeploy (remove and install) the latest version of your webapp. The bug as posted still stands, JNDI resources defined in the default context, or global resources are not accessable from webapps. Will there be a fix for this? DefaultContexts, and GlobalResources are useless if they cannot be accessed from webapps. Regards, dan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
