Return-Path: 
 <tomcat-dev-return-59398-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org
Received: (qmail 25597 invoked from network); 22 May 2005 23:44:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 22 May 2005 23:44:24 -0000
Received: (qmail 65506 invoked by uid 500); 22 May 2005 23:44:17 -0000
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 65472 invoked by uid 500); 22 May 2005 23:44:16 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 65455 invoked by uid 99); 22 May 2005 23:44:16 -0000
X-ASF-Spam-Status: No, hits=0.2 required=10.0
	tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226)
  by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 22 May 2005 16:44:14 -0700
Received: by ajax.apache.org (Postfix, from userid 99)
	id 3561F299; Mon, 23 May 2005 01:44:09 +0200 (CEST)
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 35014]  New:  -
    Please document the change in the context file XML format
X-Bugzilla-Reason: AssignedTo
Message-Id: <20050522234409.3561F299@ajax.apache.org>
Date: Mon, 23 May 2005 01:44:09 +0200 (CEST)
X-Virus-Checked: Checked
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
<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: apache-bug-db@web-startup.co.uk


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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org