Scott is correct as to the solution.
The problem: if the loading is done with
classloader.getResource("jndi.properties");
then the classloading goes parent and finds classpath ones and returns that.
This is a reason why in JBoss 2.x we use "local" CL to jars by not setting the parent
to the JB
and this should take precedence
over the values found in the classpath, but I'm not sure of the
load ordering.
- Original Message -
From: Bill Burke
To: [EMAIL PROTECTED]
Sent: Sunday, January 06, 2002 7:06 AM
Subject: [JBoss-dev] jndi props in testsuite
If I add a jndi.properties fi
I'm not at all sure...
I think that the testcase classes are not packaged into a jar at the
moment, and there is one jndi.properties on the classpath that gets used
for all of them by default. This is very handy for non-cluster tests, but
obviously may not work for you. Could you create an init
If I add a jndi.properties file to a testsuite jar,
will it use that file for InitialContext? InitialContext looks for
jndi.properties in the CLASSPATH correct?
Thanks,
Bill
