I deployed an entity bean, AllFieldsTest, and I am able to look up its home
interface, create new ones, find the ones I created, remove them, etc. from
a client program.  That is, a program not running in the app server.

I then wrote a session bean which I deployed.  I can access this from a
client program.

However, I cannot get the session bean to access the entity beans.  It
fails on the lookup of the entity bean home.  If I iterate over the jndi
namespace in the session bean and print out the bindings, I can see the
home interface for the entity bean listed.  But if I try to look it up I
get a NamingException.  I think this is related to the session bean not
being able to load the class for the entity bean home.  I say that because
if I try the following from the session bean I get a ClassNotFoundException:

    System.out.println(Class.forName("AllFieldsTestHome"));

I also tried to pass the meta data interface for the entity bean from the
client to the session bean.  This causes an UndeclaredThrowableException to
come back to the client.  Nested inside that exception is a
ClassNotFoundException.  This seems to confirm the theory that the server
cannot find the class.

I am running jBoss 2.0 FINAL under jdk1.3.  The entity bean classes are on
the classpath in the shell from which I start jBoss.  I'm not sure what
else I need to do.

I don't want to use <ejb-ref> statements in the deploymnent descriptor
because this session bean is supposed to be able to look up arbitrary
entity beans based on information passed to it.  I also believe that
<ejb-ref> is optional.  Correct me if I'm wrong.

Thanks.

- Larry
Larry Kline
[EMAIL PROTECTED]


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]

Reply via email to