Re: MessageDriven Beans !

i remember there being a bug in the JMS implementation, that it only works with one topic at the moment, here it is - bug#353 If we create multiple JMS topics only the last created topic will be served by message-driven beans who subscribed to that "last created topic". In other words, there is

Re: Help me please domain was nul message is killing me here...

i am also trying to get two orion servers talking to each other, on server A i have declared an ejb-module to be remote (orion-application.xml), this module runs on server B. Server B is declared in the rmi.xml file as another rmi server for server A, I lookup the ejb from the remote module, and

Re: JMS Temporary Topics, onMessage

Title: JMS Temporary Topics, onMessage hi, i am using orion1.4.5 on windows 2000, and have also noticed getJMSReplyTo() returning a null object, but also i can't create a subscriber to a temporary topic, i get the javax.jms.InvalidDestinationException: Invalid topic, i've submitted this as

Re: Creating subscribers in JMS

i manage to create a subscriber using topicSession.createSubscriber(Topic, null, false), I think i've seen a bug reported for the topicSession.createSubscriber(Topic), I'm using orion1.4.5, however, I get this error javax.jms.InvalidDestinationException: Invalid topic, when trying to create a

Re: Problems with JNDI lookups of ejb-ref-name defined in application-client.xml from a client application...

try: new InitialContext().lookup("java:comp/env/ejb/id"); - Original Message - From: "Alex Paransky" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Thursday, March 15, 2001 10:10 PM Subject: Problems with JNDI lookups of ejb-ref-name defined in application-client.xml

Re: Inconsistent EJB JNDI Locations

Title: RE: Inconsistent EJB JNDI Locations i'm reasonably new to this also, so i may be wrong! i have the application-client.xml in a META_INF directory which is beside my client application, so i think the client application InitialContext reads this file, it seems to work for me anyway..

Re: SOAP interface for ejb beans?

i downloaded the apache soap implementation, which has a servlet (rpcrouter) for handling soap requests. I installed the servlet as an application on Orion. I used the StatelessEJBProvider class but had to modify it a bit to get it to work with orion, (the initialise method). This class handles

want Client to block on a session bean

hi, the scenario is, Client calls method of a bean, which then invokes other beans to do some processing and waits, when processing is finished, the bean is informed and stops waiting and the method returns to the Client. I tried using wait, notify within the bean, but this did not work as

Re: SV: JNDI Lookup Failure

hi, i have defined ejb-ref name in web.xml as - ejb-ref ejb-ref-nameejb/ClientInterface/ejb-ref-name ejb-ref-typeSession/ejb-ref-type homeserene.ejb.ClientInterfaceHome/home remoteserene.ejb.ClientInterface/remote /ejb-ref The JNDI lookup should then be

Re: 2 problems with orion: restart and pageContext variable

I think for part 2. the port number 8080 maybe wrong, i don't specify a port number when using admin.jar example : java -jar admin.jar ormi://localhost admin niloc -deploy -file H:\dev\soap\rel\soap.ear -deploymentName soap so i think it uses the default port number for ormi.. colin.

ejb-ref-mapping

be much appreciated. regards colin harris..