Return-Path: 
 <tomcat-user-return-118006-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 28770 invoked from network); 17 Dec 2004 10:34:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 17 Dec 2004 10:34:12 -0000
Received: (qmail 32677 invoked by uid 500); 17 Dec 2004 10:33:58 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 32657 invoked by uid 500); 17 Dec 2004 10:33:57 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 32642 invoked by uid 99); 17 Dec 2004 10:33:57 -0000
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from ev1s-216-127-94-29.ev1servers.net (HELO ensim.rackshack.net)
 (216.127.94.29)
  by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 17 Dec 2004 02:32:01 -0800
Received: from roman (80-28-25-134.adsl.nuria.telefonica-data.net
 [80.28.25.134])
	(authenticated (0 bits))
	by ensim.rackshack.net (8.11.6/8.11.6) with ESMTP id iBH9xNk09607
	for <tomcat-user@jakarta.apache.org>; Fri, 17 Dec 2004 10:59:23 +0100
Message-ID: <00c701c4e41e$564a7ad0$7b00a8c0@roman>
From: =?iso-8859-1?Q?Rom=E1n_Pena?= <rpena@publicinet.net>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
References: <E4321639A20B06448CB83BC03A1D665C14C2B2@server01.reeher.net>
Subject: Re: tomcat 5.5 and jndi context naming error
Date: Fri, 17 Dec 2004 10:54:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N


----- Original Message ----- 
From: "Ken Hall" <ken.hall@reehergroup.com>
To: <tomcat-user@jakarta.apache.org>
Sent: Thursday, December 16, 2004 10:41 PM
Subject: tomcat 5.5 and jndi context naming error


>Since downloading the new version of Tomcat 5.5.4, I have been
>experiencing problems with jndi resources within my web app. I am
>porting over from an existing server where that resource is working.

I think you shoud change your config. From 5.0 to 5.5, the context xml
files have changed. Now, instead of using resource params, you should
use attributes in the Resource tag. Change this:

    <Resource auth="Container"
              name="jdbc/myapp"
              type="javax.sql.DataSource"/>

    <ResourceParams name="jdbc/myapp">
      <parameter>
        <name>maxWait</name>
        <value>5000</value>
      </parameter>
      (...)
    </ResourceParams>  

To this:

    <Resource auth="Container"
              name="jdbc/myapp"
              type="javax.sql.DataSource"
              maxWait="5000"
              (...)
    /> 

 

I had the same problem, but it took me some time and headaches to
notice the documentation had changed. Maybe the docs for 5.5
should have reflected the changes with BIG RED LETTERS or so.
I'd want the people at the Jakarta project to think of it:
If you save half an hour to each developer or admin who migrates
to 5.5, maybe you are saving 2 or 3 lives a month :D
--Steve jobs way of thinking ;)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org