Re: RMI client accessing JMS Topic

2002-03-20 Thread Kesav Kumar
a" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Tuesday, March 19, 2002 10:12 PM Subject: Re: RMI client accessing JMS Topic > Hello Kesav, > > Thanks for your reply. It seems to me that the problem occurs when the client > is not a J2E

Re: RMI client accessing JMS Topic

2002-03-19 Thread Vidur Dhanda
Hello Kesav, Thanks for your reply. It seems to me that the problem occurs when the client is not a J2EE application client. Hence, the application-client.xml is not available. Did you modify the JMSChat example to not use the java:comp/env namespace? I believe a RMI client will not have acce

Re: RMI client accessing JMS Topic

2002-03-19 Thread Kesav Kumar
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yes you can use RMIInitialContextFactory to get the connection factory. I just modified the JMSChat program in the demo to use RMIInitialContext and I am able to get the factory and topic. Are you running this client program from different machine f

Re: RMI client accessing JMS Topic

2002-03-19 Thread Vidur Dhanda
Hi Peter, The Orion console correctly shows jms/notificationFactory. It is only when the RMIContext.lookup happens that the client hangs. I am beginning to suspect that this is a bug. Has anyone successfully used a TopicConnectionFactory via a RMIClient? Vidur "SAURUGGER,PETER (A-PaloAlto,ex

RE: RMI client accessing JMS Topic

2002-03-19 Thread SAURUGGER,PETER (A-PaloAlto,ex2)
I found it useful to look at OrionServers console, under context; in general, it seems all objects get exposed under the root context with their full qualified pathname, in your case probably something like context.lookup("com.epistemic.notification.NotificationFactory") or whatever ... -Orig