Hi Alex,
        Thanks for the immediate response. I have checked. Its present both in JBoss and tomcat classpath. As I mentioned in the earlier mail, this happens only on some scenario(also re-producable). But it works fine for other scenario's. Hence the confusion.

Thanks
-M

At 13:02 10/06/2003 +0300, you wrote:
There should be jnp-client.jar in %JBOSS_HOME%\client. Make sure it is
in client's classpath.

alex

Tuesday, June 10, 2003, 12:33:04 PM, Muraly R wrote:

MR> Sorry, this time with stack trace attached...:-)

MR> -M

MR> At 14:22 10/06/2003 +0530, you wrote:
>>Hi Gurus,
>>         I am actually stuck with this error scenario. The flow for the
>> scenario is there is lookup portion in my client code(i.e tomcat separate
>> installation), which looks up JBoss server(3.0.4) for a session bean.
>> This works fine, except in some scenario's the following error is thrown:
>>
>>ERROR 10/Jun/2003 13:49:13 [Thread-34] (HomeReferencesManager.java:106):
>>util.HomeReferencesManager - Cannot instantiate class:
>>org.jnp.interfaces.NamingContextFactory
>>
>>java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
>>
>>I have jnp-client.jar in the client classpath.
>>
>>Have any one encountered this scenario before? Please share your thoughts
>>on the same.
>>
>>The most confusing(irritating actaully) part is, the same bean lookup from
>>the same code snippet location works fine in some scenarios.
>>
>>Thanks
>>Muraly



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to