My guess is the Orion is assuming my EJB is a 1.1 entity
bean. What tell Orion that the bean is a 2.0 bean?
Perhaps that is where my mistake lies.
-tim
> -----Original Message-----
> From: John D'Ausilio [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 18, 2000 3:28 PM
> To: Orion-Interest
> Subject: RE: support EJB2.0 or not?
>
>
> You need to examine your deployment descriptor and
> class/interface defs ..
> there are lots of rules to follow, and they're easy to miss.
> I have CMP
> beans and dependent objects in various types of relationships
> all running
> just fine, but I've spent many an hour trying to find
> mistakes evidenced by
> errors such as yours. Go through the contract in section 9 of
> the spec, and
> assume nothing :)
>
> (I wish I could remember just which mistake it was that
> caused that problem,
> but I cant)
>
> jd
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Drury
> > Sent: Wednesday, October 18, 2000 12:18 PM
> > To: Orion-Interest
> > Subject: support EJB2.0 or not?
> >
> >
> >
> > When I try to write a 2.0 compliant entity bean:
> >
> > public abstract class ContactBean implement EntityBean
> > {
> > public abstract void setName(String s);
> > public abstract String getName();
> > ...
> >
> > }
> >
> > Orion throws the error (at deployment):
> >
> > ... Bean class com.tfc.ejb.ContactBean must not be declared
> > abstract
> >
> > So what did I do wrong? Does Orion 1.3.8 or 1.4.0 support
> > EJB 2.0 entity beans like the web page advertises or not?
> >
> > -tim
>
>
