I've come up with a workaround to the problem that Tomcat servlets can't seem to find
the jndi.properties file and
thus connect to an external JBoss server.
Hardcoding the properties works, but is ugly since then your code is tied to the
specific location of the JBoss
server.and thus
This works for me:
// Try to find each of these individual parameters
// and construct the properties
// object appropriately
java.util.Properties p = new java.util.Properties();
p.put(InitialContext.INITIAL_CONTEXT_FACTORY,
org.jnp.interfaces.NamingContextFactory);
Hi,
Where do the org.jnp classes come from?
Thanks,
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Becker, Michael [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 9:35 AM
To: Tomcat Users List
Subject: RE: Tomcat with external JBoss (JNDI problems
Copy %JBOSS_HOME%/client/[jboss-client.jar,jboss-common-client.jar,
jbosssx-client.jar, jnp-client.jar, jboss-j2ee.jar, and log4j.jar] to
%CATALINA_HOME%/shared/lib.
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
Hi,
Where do the org.jnp classes come from?
Thanks,
Copy %JBOSS_HOME%/client/[jboss-client.jar,jboss-common-client.jar,
jbosssx-client.jar, jnp-client.jar, jboss-j2ee.jar, and log4j.jar] to
%CATALINA_HOME%/shared/lib.
Doesn't work.it still does not pick up my JBoss-specific jndi.properties file.
I've got that file in the WEB-INF/classes
Copy %JBOSS_HOME%/client/[jboss-client.jar,jboss-common-client.jar,
jbosssx-client.jar, jnp-client.jar, jboss-j2ee.jar, and log4j.jar]
to
%CATALINA_HOME%/shared/lib.
Doesn't work.it still does not pick up my JBoss-specific
jndi.properties file.
I've got that file in the
.
- Original Message -
From: Andrzej Jan Taramina [EMAIL PROTECTED]
To: Becker, Michael [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, November 22, 2002 6:39 PM
Subject: RE: Tomcat with external JBoss (JNDI problems)...
Copy %JBOSS_HOME%/client/[jboss-client.jar,jboss-common-client.jar
I ran into the same problem and decided to address this by making all of
the parameters JNDI environment variables and configuring those params in
my web.xml file. I can easily change the configuration by commenting out
or changing the environment entries in my web.xml file. Eventually, I
I've come up with a workaround to the problem that Tomcat servlets can't seem to find
the jndi.properties file and
thus connect to an external JBoss server.
Hardcoding the properties works, but is ugly since then your code is tied to the
specific location of the JBoss
server.and thus
