I believe your last assertion is false. Any entity bean that has a composed
key (that is, its key maps to more than one field in the persistence) must
have its own PK class
check the specs
JP
-----Original Message-----
From: Oglinda [mailto:[EMAIL PROTECTED]]
Sent: Sábado, 20 de Enero de 2001 22:35
To: Orion-Interest
Subject: Re: E_Roman e-commerce application(Mastering Java Beans)Wiley
At 01:31 AM 1/20/01 +0000, faisal wrote:
>Hi
>-Has any body tried to install Ed Roman e-commerce examples on Orion?.
I am studying the book and I have played with some of the EJBs. There are
some problems
1. I assume the code was written with the EJB 1.0 specifications because it
is using some deprecated methods.
2. The author was using WebLogic to deploy the beans and there are some
major differences in the way you deploy the EJBs.
> -Another question is it possible to do without creating a seperate class
> for the primary key such as "customerPK.class"
I am not an expert but from what I have noticed:
* CMBs do not need a PK class
* Bean-Managed persistence requires a PK class.
Danut
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
