Hi Jeff...
Thats odd. I don't have <cmp-version> 2.x </cmp-version> specified anywhere
in my descriptor. Nor do I have any indication in my application.xml file
that it should use EJB 2.0. And, as you know, I also have a bunch of EJB
2.0 CMP entity beans.
I started my ejb-jar.xml file by copying the one from the ATM sample. It
does not have that either. There is nothing in the server.xml file about
it. So I wonder, how does Orion it know? I assumed it guessed by looking at
the code, so prehaps he should post the code for his entity bean as well?.
Jim
PS - Did you know that whatever you use for a mail server routinely has
trouble accepting mail? I always get the 4 hour can't send warning from my
outgoing mail server.
--On Wednesday, October 18, 2000 10:12 PM -0700 Jeff Schnitzer
<[EMAIL PROTECTED]> wrote:
> No, you don't need to specify the new DOCTYPE. I haven't, and I'm
> making extensive use of EJB2.0 beans.
>
> Tim, you probably are missing something important in the deployment
> descriptor. It's hard to say what without seeing it. Do you have
>
> <cmp-version> 2.x </cmp-version>
>
> in your <entity> block? You should post your descriptor if you would
> like further help.
>
> Jeff
>
>> -----Original Message-----
>> From: John D'Ausilio [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, October 18, 2000 4:59 PM
>> To: Orion-Interest
>> Subject: RE: support EJB2.0 or not?
>>
>>
>> I believe the difference is in which dtd you specify in the deployment
>> descriptor DOCTYPE
>>
>> > -----Original Message-----
>> > From: [EMAIL PROTECTED]
>> > [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Drury
>> > Sent: Wednesday, October 18, 2000 5:21 PM
>> > To: Orion-Interest
>> > Subject: RE: support EJB2.0 or not?
>> >
>> >
>> >
>> > 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
>> > >
>> > >
>>
>>
>>
