Take a look at http://issues.apache.org/bugzilla/show_bug.cgi?id=4690
and see if this accurately describes the issue you are having. This is
a known incompatibility with the servlet spec that has been in place for
over a year. If this is your problem, at least try to vote for it so
that it can
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);
,
-Original Message-
From: Becker, Michael [mailto:[EMAIL PROTECTED]]
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
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
Eddie,
There is a known issue with cross-context communication and sharing
information between the sessions
(http://issues.apache.org/bugzilla/show_bug.cgi?id=4690).
Unfortunately, I ran into the same issue and had to write a hack in my
environment. I already had a custom realm, so I modified it
Hey all,
I'm currently running IIS as the front-end to Tomcat 4.1.12 using the
JK2 2.0.1 release of isapi_redirector2.dll. When I use the
CoyoteConnector, it authenticates for me (creates a Principal for me)
and does not pass information to my Realm implementation. When I use
the Ajp13Connector
