Here is how I think it works.
The system registers the fully qualified classnames at the server side when
starting the server. Yes, I'm assuming that fqnames are registered.
When the client container starts, the client-application.xml is loaded and
the system checks whether it can find locally the classes mentioned in the
remote and home references.
When the client references one of the ejb-refs the client container lookups
in fact the fully qualified classname from the naming service and
'connects' to the server bean.
Why I'm presuming it works like this? Look what happens when you move the
classes from one package to another on the server (in a working example).
You get the same error messages as you guys experiencing.
FE
-----Original Message-----
From: Todd McGrath [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 2:36 AM
To: [EMAIL PROTECTED]
Subject: RE: How to access EJB's from client (not packaged in .ear) ?
Frank,
I came across post of yours in the Orion mailing list. I'm trying to
access
EJBs on one Orion machine from servlets on another Orion machine. I'm not
having any luck and I came across your modified orion-primer example, which
I thought we be a good step for me to take.
I seem to be having a similar issue to Daniel. I successfully deployed on
Server A and now when I run the client from Server B:
I get an initial context fine, but I always end up with NoClassDefFound
errors when attempting to grab the Home interface.
Any suggestions?
Regards,
Todd
