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=24723>.
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=24723

JNDI Datasource HOWTO instructions incorrect - Name jdbc is not bound in this Context

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2004-05-27 18:39 -------
OK.  I've modified the document to address the issues you raised.  You can see 
it in CVS at http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-
catalina/webapps/docs/jndi-datasource-examples-howto.xml and it will of course 
be part of future tomcat 5 releases.  It will be visible on the website with 
the next tomcat 5 release.

In addition, I've verified the how-to works exactly as specified when following 
the document to the letter, against Oracle and MySQL, on tomcat 5.0.25 (the 
latest stable release at the time of this writing).  I did this verification 
putting the data source declarations both inside a Context and inside the 
GlobalNamingResources: both work equally well.

I have not tested admin webapp editing of these data sources.  If a bug exists 
there, feel free to submit another issue in bugzilla: this issue is for the 
documentation flaws.

Finally, if you feel like the documentation is still lacking / misleading / 
wrong, I restate my earlier invitation for you to submit the text changes you'd 
like to see, and my earlier promise to quickly review and commit them.

This bug is not invalid: it's valid, and it's now fixed.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to