Yes, none of the client jars should be including jndi.properties files as it does make it difficult to track down configuration problems.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Fusayuki Minamoto wrote:
Is it troublesome that the jbossjmx-ant.jar includes a jndi.properties?
If a user puts the the jbossjmx-ant.jar on the client classpath by mistake, that may hide his real jndi.properties and then causes an error at JNDI lookup.
It must be hard for him to find why such an error occures in spite of a fact that the correct jndi.properties is set on the client classpath.
Sorry for the tedious response, but I'd let you know this just because a friend has come across this trouble recently.
Miki
From: Jon Haugsand <[EMAIL PROTECTED]> Subject: Re: [JBoss-user] jbossjmx-ant.jar Date: Fri, 20 Jun 2003 13:59:59 +0200
* Jon Haugsand
Trial and error showed me that the file jbossjmx-ant.jar was necessary to run a stand-alone client program towards my JBoss application.
I naively thought that the file jbossall-client.jar was enough. Why is that? (JBoss 3.2.1)
Without it, I get the following error:
Ok, I found it myself. The file jndi.properties is included in this file, and the one I served in another place looked like this:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces #java.naming.provider.url=jnp://localhost:1099
That is, I had commented out the java.naming.provider.url property. However, I always thought this was correct.
-- Jon Haugsand, [EMAIL PROTECTED] http://www.norges-bank.no
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
