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=35014>. 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=35014 Summary: Please document the change in the context file XML format Product: Tomcat 5 Version: 5.5.9 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Webapps:Documentation AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Have just spent 3 days stuck on upgrading a working webapp from 5.0.28 to 5.5.9, I finally solved it with help from tomcat-user, but I can't find the core issue mentioned in the TC docs. I therefore humbly suggest it might be a useful note to include in the docs for 5.5 (and maybe 5.0 too, as a warning that the approach that was previously valid in 5.0 is now invalid in 5.5). Also, might it be a good idea to include this in future 5.5.x release notes? Basically, under 5.0.28 I had a separate xml context config file within my warfile/META-INF, that used the nested-tag approach, i.e. <ResourceParams> <parameter> </parameter> </ResourceParams>, but this did not work under 5.5.9, which seems to require the single-tag <Resource/> approach. I recognise that the JDBC how-to page example uses the new approach, but it makes no comment about the previous approach being invalid, perhaps it would help those upgrading if the change was explicitly mentioned? I say this particularly in view of the fact that TC offers several ways to config a context, so it might be helpful to clarify that here is one way that is no longer valid in 5.5. The reported exception was "No suitable driver" from java.sql.DriverManager, which is why I did not initially suspect an XML problem. This is a second reason why this is a tricky one to solve without help from the docs. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
