Return-Path: 
 <torque-user-return-6581-apmail-db-torque-user-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-torque-user-archive@www.apache.org
Received: (qmail 41163 invoked from network); 17 Nov 2005 21:53:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 17 Nov 2005 21:53:38 -0000
Received: (qmail 30562 invoked by uid 500); 17 Nov 2005 21:53:37 -0000
Delivered-To: apmail-db-torque-user-archive@db.apache.org
Received: (qmail 30544 invoked by uid 500); 17 Nov 2005 21:53:37 -0000
Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:torque-user-unsubscribe@db.apache.org>
List-Help: <mailto:torque-user-help@db.apache.org>
List-Post: <mailto:torque-user@db.apache.org>
List-Id: "Apache Torque Users List" <torque-user.db.apache.org>
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Delivered-To: mailing list torque-user@db.apache.org
Received: (qmail 30533 invoked by uid 99); 17 Nov 2005 21:53:37 -0000
X-ASF-Spam-Status: No, hits=-10.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 17 Nov 2005 13:53:36 -0800
Received: (qmail 41077 invoked by uid 1977); 17 Nov 2005 21:53:16 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 17 Nov 2005 21:53:16 -0000
Date: Thu, 17 Nov 2005 13:53:16 -0800 (PST)
From: Thomas Fischer <tfischer@apache.org>
To: Apache Torque Users List <torque-user@db.apache.org>
Subject: Re: Initialization of JndiDataSourceFactory fails
In-Reply-To: <5EE5137D79A3CA45970354F512B3F3E339E2E8@m-ex1.gt.local>
Message-ID: <20051117134204.B30911@minotaur.apache.org>
References: <5EE5137D79A3CA45970354F512B3F3E339E2E8@m-ex1.gt.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Rating: localhost 1.6.2 0/1000/N
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

I remember that upgrading to commons-configuration-1.1 has caused some 
problems in the past. It was something like returning empty lists instead 
of null asking for a subset-configuration, but I cannot remember exactly.

Just a shot in the air: Maybe you want to take over the initialisation 
code (i.e.TorqueImpl.java) from 3.2-rc3 and repackage the Torque runtime 
jar (no idea whether it is binary compatible at all).

If you have the possibility to debug the initialisation methods in 
TorqueImpl, you should do so. The code is not difficult tu understand. 
If you cannot debug easily, you might want to get the source, plaster it 
with log messages, and recompile it.

Maybe this is also the time to switch to a newer Torque version ? I have 
3.2-rc1 in production (with some customisation) using oracle (with the 
lob-enhanced village) and it runs with configuration-1.1 without any 
problems.

    Hope that helps,

         Thomas

On Thu, 17 Nov 2005, Vitzethum, Daniel wrote:

> Hello Greg,
>
> thx for your quick answer!
>
>> First, what version of Torque are you using?
>
> Believe me, I really had in mind _not_ to forget it! Ouch!
> I'm using Torque 3.1.
>
>> Second, what torque.dsfactory.<db>.datasource properties are
>> set in your Torque.properties file?
>
> None? This is all I needed in two or three other Projects, some
> on Tomcat, some on Bea:
>
> ----8<----
> torque.applicationRoot = <db>
> torque.database.default = <db>
> torque.database.<db>.adapter = oracle
>
> ## Using jndi - datasource from container
>
> torque.dsfactory.<db>.factory=org.apache.torque.dsfactory.JndiDataSource
> Factory
>
> # 4 Tomcat (unused here)
> #torque.dsfactory.<db>.jndi.path=java:comp/env/jdbc/ZeusDS
> # 4 Bea
> torque.dsfactory.<db>.jndi.path=jdbc/ZeusDS
> ----8<----
>
> By now I thought the DS comes from the container...
>
>> You need to specify a torque.dsfactory.<dbname>.datasource.classname
>> property in the Torque.properties file.
>
> See above. Do I really have to? I didn't had to by now.
>
>> Or that your bind string doesn't match what BEA uses internally AFAIK,
>> there is no true "standard" for how a servlet engine structures JNDI
> tree
>> internally. The one used by Tomcat is becoming the "defacto" standard,
>> but BEA might do things differently.
>
> That's what it does, but we handled both Bea and Tomcat earlier.
>
>
> We got a bit further now:
>
> we were using Torque not with ist original dependencies, but migrated
> from
>  commons-configuration-1.0-dev-3.20030607.194155.jar
>  to
>  commons-configuration-1.1.jar
> and from
>  commons-lang-1.0.1.jar
>  to
>  commons-lang-2.0.jar.
>
> Can anybody imagine that this is the cause of the "bind" exception? When
> returning
> to the original libs, it seems to work. (We can't do that in our
> project, however.)
>
>
> Any hints appreciated... ;-)
>
>
> Daniel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
>

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