Thanks for the response Peter! :)
Ah, yes, the exception is a NamingException. It happens when the client
tries to use the INITIAL_CONTEXT_FACTORY and PROVIDER_URL provided in
the JBoss jndi.properties file to get the initial context.
This code, (the client and the session bean), comes from the WebLogic
stateless session bean example, and the bean is deploying fine under
JBoss, and the client works fine under WL, so I assume it's some piece
I've missed in setting up JNDI, but I can't quite find enough
information online to figure out what I'm to do when setting up JNDI for
JBoss.
Thanks for any and all help.
Patti :)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: None
To: jBoss
Subject: Re: [jBoss-User] Connecting a client to a deployed session bean
Patti,
I assume you're getting an exception? What exception is being thrown??
cheers,
peter
<pre>
Hi,
I'm having difficulty getting a client to connect to a bean I've
successfully deployed in the JBoss server. This bean and client work
fine under WebLogic. Hopefully one of y'all can see what I'm doing
wrong.
I'm using the JNDI values in the jndi.properties file for the context
lookup, but never get a connection.
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=localhost
Is there something else I need to do, like maybe 'tween JNDI and LDAP?
Thanks!
Patti :)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
</pre>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
