Return-Path: 
 <cocoon-users-return-34298-apmail-xml-cocoon-users-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org
Received: (qmail 67059 invoked by uid 500); 30 May 2002 17:06:59 -0000
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-users-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-users-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-users@xml.apache.org>
Reply-To: cocoon-users@xml.apache.org
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 67048 invoked from network); 30 May 2002 17:06:58 -0000
Reply-To: <bloritsch@apache.org>
From: "Berin Loritsch" <bloritsch@apache.org>
To: <cocoon-users@xml.apache.org>
Subject: RE: PostgreSQL won't work - any ideas appreciated 
Date: Thu, 30 May 2002 13:06:43 -0400
Message-ID: <002701c207fc$60b45820$ac00a8c0@Gabriel>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <200205301557.g4UFvUDa016915@mira.taygeta.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> From: Skip Carter [mailto:skip@taygeta.com] 
> 
> > Once I get this figured out I PROMISE TO CREATE DOCUMENTATION :)
> 
> 	I have PostgreSQL working just fine here.  I had to add the
>         location of postgres.jar to the classpath in catalina.sh
>         since it is not normally in the default classpath on 
> my system.
> 
> The line in catalina.sh:
> 
> CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/bootstrap.jar
> 
> was changed to:
> 
> CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/bootstrap.jar:/usr
> /local/java/postg
> resql.jar
> 
> 
>    The <dburl> element of cocoon.xconf is just a reference to 
> the database URL for that particular data source:
> 
>    <dburl>jdbc:postgresql://dbserver.example.com:5432/books</dburl>


Having written the datasource pooling code, I am aware of what the
<dburl/> entry is supposed to be.  I was saying that you might want
to include the <driver/> element with the classname to that entry
in cocoon.xconf.

Regarding the location of the Driver jars, there are three solutions:

1) Include it in the WEB-INF/lib directory in your webapp
   * It is always included with the webapp
   * No additional install step is necessary
   * Not all servlet containers respect the WEB-INF/lib contract
     (IBM WebSPhere moves the libs, but most current containers
     work properly now).

2) Include it in the $JAVA_HOME/jre/lib/ext directory
   * It is available to all Java applications on the machine
   * It is an additional install step, but simple to do.
   * If the webapp is moved, you have to make sure the driver
     exists on the new machine or new JVM.

3) Do what you did and alter the Servlet Container's default
   CLASSPATH.
   * It is available to all webapps in the contianer
   * It is an additional install step, and in some cases not trivial
   * Each servlet container has a different method of doing this,
     and some don't allow it at all.

Of the three, 1 or 2 is preferred.  2 should only be considered for
jars that are not likely to cause a conflict like a database driver.
While the first option works 90% of the time, you do end up with
duplicate drivers.  It is not the end of the world though.


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail: <cocoon-users-help@xml.apache.org>