Quoting Arthur T Smyles <[EMAIL PROTECTED]>:
> While I understand that J2EE spec has a standard way of getting
> resources,(including I imagine other JNDI Contexts), I still think that
> this
> approach should also be allowed for the following reasons:
Ok, I don't really know what we're talking
ause OTHER projects don't allow
it doesn't mean Tomcat shouldn't :)
Arthur
[EMAIL PROTECTED] on 01/30/2001 06:35:39 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Arthur T Smyles)
Subject: Re: Custom ObjectFactory w\ Tomcat 4.0beta1
Quotin
Quoting Arthur T Smyles <[EMAIL PROTECTED]>:
> Thanks for you quick response. It has though brought about more
> questions. For
> example, if I had the following code
>
> Hashtable env=new Hashtable();
> env.put("java.naming.factory.initial","com.sun.jndi.ldap.LdapCtxFactory");
> env.put
("java.
he issues that prevent Tomcat from following this convention?
Also, I took a look at org.apache.naming packages but I am unsure which classes
are affecting this?
Arthur
[EMAIL PROTECTED] on 01/30/2001 04:36:33 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Arthur T S
> I developed an JNDI ObjectFactory that is used to read User Objects from
LDAP.
> When I run a test program and perform a lookup it works fine. But when I
use it
> within Tomcat 4.0 it ignores the java.naming.factory.object and
> java.naming.factory.state attributes that I am setting when creatin
I developed an JNDI ObjectFactory that is used to read User Objects from LDAP.
When I run a test program and perform a lookup it works fine. But when I use it
within Tomcat 4.0 it ignores the java.naming.factory.object and
java.naming.factory.state attributes that I am setting when creating the
In
