I ran into a similar problem in Weblogic. Just because the jar files are
successfully deployed doesn't mean they know about each other. Another
way to solve this is to include the jar files in the runtime classpath.
Scot.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 11/14/00, 8:29:51 AM, Rickard �berg <[EMAIL PROTECTED]> wrote regarding
Re: [jBoss-User] External ejb reference:
> Hi!
> "Nortje, Andrew" wrote:
> > I am try to use external ejb references. The ejb's are running under the
> > same jBoss server but deployed in two different jar's. I have followed
the
> > jBoss documentation (a cut and paste is given below). In the jboss.xml I
> > have replaced the jndi-name with the jndi-name of Bean B (the
documentation
> > example illustrates bean B running in another server)
> >
> > I get the exception
> >
> > [Customer] Exception: java.lang.NoClassDefFoundError: BHome
> >
> > Now I can use both Bean A and B independently from a client, so I know
they
> > are properly deployed and bound in the jndi tree, however Bean A is
unable
> > to use Bean B.
> Have you included B's interfaces in A's jar?
> /Rickard
> --
> Rickard �berg
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
