aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Orion server and the magic of RMI? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Orion server and the magic of RMI?" Watch "Orion server and the magic of RMI?" New topic
Author

Orion server and the magic of RMI?

paul wheaton
Trailboss

Joined: Dec 14, 1998
Posts: 20729
    ∞

Orion's docs says that it will make the stubs for me on the fly.
So if I have a stand alone application accessing an EJB in an Orion server... the stub object will be sent over the network? (I seem to remember something about RMI doing this)
Or, is it that the only client that can talk to an Orion EJB something within the Orion J2EE server?

permaculture Wood Burning Stoves 2.0 - 4-DVD set
Jim Baiter
Ranch Hand

Joined: Jan 05, 2001
Posts: 532
As long as your app can get a JNDI context it can do a look up and get a reference to the remote interface of the bean. This interface is a subinterface of EJBObject which is a subinterface of the java.rmi.Remote so you are correct - RMI is involved.
Paul Medford
Ranch Hand

Joined: Aug 28, 2001
Posts: 33
I am also confused.
I installed Orion 1.5.2 and I created a stand alone app. Now, it's working, but it does not mean that I understand what's going on...
The EJB books and the J2EE Tutorial say that at deployment time stubs and skeletons are created and are needed by a stand alone app to connect to the EJB server.
Well Orion does not seem to create any stubs/skeletons.
I created the three EJB classes Bean/HomeRemote/Remote, META-INF/ejb-jar.xml, which I put into myapp-ejb.jar.
Then I put this jar inside the myapp.ear with META-INF/application.xml.
Then I deployed it in Orion.
For the client, I have a jndi.properties file, 1 Client class, the original HomeRemote/Remote interfaces, and META-INF/application-client.xml.
Note: I had to put the ejb.jar (8Kb) and orion.jar (2Mb) in my client Classpath.
That's it, and everything works well.
1) So where are the stubs and skeletons???
2) While I can include the ejb.jar (8Kb) in my client lib directory, I can't deploy my app with the original Orion jar (2Mb).
Any thought?
Thanks,
Francois
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Orion server and the magic of RMI?