Return-Path: 
 <tomcat-user-return-113753-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 56513 invoked from network); 27 Oct 2004 23:04:20 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 27 Oct 2004 23:04:20 -0000
Received: (qmail 40774 invoked by uid 500); 27 Oct 2004 23:03:51 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 40712 invoked by uid 500); 27 Oct 2004 23:03:50 -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 40699 invoked by uid 99); 27 Oct 2004 23:03:50 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from [194.217.242.88] (HELO anchor-post-30.mail.demon.net)
 (194.217.242.88)
  by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 27 Oct 2004 16:03:49 -0700
Received: from steve-kirk.demon.co.uk ([80.177.0.37] helo=sjklaptop)
	by anchor-post-30.mail.demon.net with esmtp (Exim 4.42)
	id 1CMwpV-00055d-0I
	for tomcat-user@jakarta.apache.org; Wed, 27 Oct 2004 23:03:46 +0000
From: "Steve Kirk" <tomcat-user@web-startup.co.uk>
To: "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
Subject: RE: JNDI DataSource GlobalResources problem
Date: Thu, 28 Oct 2004 00:03:28 +0100
Message-ID: <000201c4bc79$2dffcca0$0201a8c0@sjklaptop>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
In-Reply-To: <9C5166762F311146951505C6790A9CF801FC395C@US-VS1.corp.mpi.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Yoav said (re: context.xml files):
> They're a TC-only feature.  Other containers go about it different =
ways.
and:
> Context.xml files are NOT designed to increase portability at all.
> They're a convenience feature.  In fact, they're a sinkhole for
> beginners to REDUCE their portability in favor of short-term
> convenience.  That's why I don't like them.

OK, got all that.  But now I've thought it all through again, it's not =
clear
what the "right" way to do it is.  In other words how should I look to
configure <Resource> and/or <Context> elements so that I can move beyond
"beginner" ?  ;)

All the alternative ways of configuring a webapp <Resource> seem to have
something against them from the point of view of portability, since they =
all
use server.xml or context.xml, which as I understand it are both
TC-proprietary.  I note that the TC docs currently recommend using
context.xml within either the conf folder or the warfile, rather than
including <Context> within the server.xml itself, but both of these
recommened approaches seem to be non-portable to other containers....?



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