Ben,
>From page 169 of Oreilly's Enterprise JavaBeans 2nd Edition:
The ejbCreate() method returns void in EJB 1.0 and a null value of type
ShipPK for the bean's primary key in EJB 1.1. The end result is the same:
in both EJB 1.0 and EJB 1.1, the return value of the ejbCreate() method for
a conta
The point is that the declaration of your ejbCreate() must specify that you
will return the PrimKeyClass. In the implementation of the ejbCrate() however
you just return null - a PrimKeyClass null.
That's how I do it and that's what I think is correct with respect to the
spec.
Yours
Armin Mi
It's null but the return type of ejbCreate is always the primary key class
never void.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ben
> Christensen
> Sent: Monday, May 14, 2001 8:15 PM
> To: Orion-Interest
> Su
-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ben
> Christensen
> Sent: Monday, May 14, 2001 8:15 PM
> To: Orion-Interest
> Subject: CMP Primary Key and ejbCreate
>
>
> When I generate a CMP bean with a Primary Key Class, it compiles and
> pa
When I generate a CMP bean with a Primary Key Class, it compiles and
packages fine as far as the java side is concerned, however, when it is
deployed, it has an issue.
According to page 69 of the J2EE developers guide (I checked to be sure
I wasn't just talking about anything), it says that if th
