the create method must reside in the Home interface and must match an
ejbCreate method in the bean class...
the Home And Remote interfaces (Login.java and LoginHome.java) must be
implemented somewhere,
because the Bean class doesn't implement it...
EJB Servers/Containers, at deploy time, build a class that implements them
and calls your ejb--
providing an indirection pattern which enables to provide transaction,
security, caching and pooling support
I suggest you read (again) extra carefully the ejb spec, and don't skip any
section, specially the ones about
Container responsabilities, this will give you the insight to know why your
app isn't behaving well...
HTH,
Rifle
PS: Copies of your Login*.java and the ejb-jar.xml would be welcome...
-----Original Message-----
From: Duffey, Kevin [mailto:[EMAIL PROTECTED]]
Sent: Viernes, 20 de Octubre de 2000 17:22
To: Orion-Interest
Subject: RE: EJB Help..
HI,
> Double check your ejb-jar.xml--are you setting LoginHome as your Home
> interface in there? Is there a LoginHome.create() method
> declared? Is there
> a LoginBean.ejbCreate() method defined?
Hmm..I don't have a LoginHome.create()..the Orion Primer didn't show that. I
have a Login.java, LoginBean.java and LoginHome.java. I think Login.java is
the only one with a create() method in it. Should both the "interface"
classes have a create() in it?
Also, why is Orion trying to compile it if its already compiled? Or is this
some sort of "assembly" routine Orion does? I assume from what I read that
the EJB server "implements" the interfaces..so is it generating its own code
at runtime and that is what compiling is failing?
Thanks again.
