Hi Michael, If I understand your post here, I think you have a terminology question about the term application. For Orion and recent versions of the other popular appservers the term *application* refers to the collection of classes, html files, and such that you package up and deploy as a single unit typically in a single ear file. One could have multiple applications deployed on an appserver. Your application could only consist of a single EJB, and it doesn't need to know about every EJB client that calls upon it. The only thing your EJB client needs are the stubs, support and server connection classes, and some sort of name of the home object. I have found that for Orion, as compared to some of the other popular appservers, the EJB client (remote client anyway) needs to go through their security system which involves specifying the name of the application that contains the EJB and username/password credentials to get the reference to the EJB's home object.
I hope this helps, Chris Thompson Bean-test Developer http://www.empirix.com -----Original Message----- From: Michael Remijan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 10:50 AM Subject: having trouble understanding what an EJB client application is Hi all, This may sound like a strange question but I'm wondering if someone could clarify for me what an EJB client application is considered to be. Let me explain why i'm confused about this. My application server experience is with JBoss. With JBoss I can use the sun's DeployTool application that downloads with the j2ee sdk to create an EAR of only beans, deploy those beans to JBoss, and then create as many clients as I want (gui apps, servlets, console apps, etc) that access and use those beans. This is very nice because for each bean I can create a simple test application for unit testing to make sure it works. At the same time, another development team can be working on the real application that uses the beans. As long as the beans are deployed on JBoss we have no problem using them. Recently I've started looking at the Orion application server. This seems to be radically different. I still able to use DeployTool to create an EAR of only bean and deploy those beans to orion. However, client applications don't seem to be able to get to the beans. It looks like in orion a "client" application must be deployed in the EAR with the beans. I can see how this might work with a web application since orion is its own web server...orion runs the application for you. But I have no clue how this works if your "client" is a gui application. Does the gui application need to be deployed with the EAR and installed on a customer's machine in order for it to use the beans? why? what does one have to do with the other? I was under the impression that I can develop Beans, deploy them, and then whoever, whereever could use them. If everytime the whoever, wherever create a new application, or update their application causes me to have to re-deploy and ear with there application that seems to be a very poor design. Thanks, Mike __________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
