I was just looking at the EJB 2.0 spec, and saw this:
"The container managed persistent fields and container managed relationship
fields must *not* be defined in the entity bean class. From the perspective
of the Bean provider, the container managed persistent fields and container
managed relationship fields are *virtual* fields only, and are accessed
through get and set accessor methods. The implementations of the container
managed persistent fields and container managed relationship fields is
supplied by the Persistence Manager."
I.e. in EJB 2.0 you don't code the CMP persistence fields yourself. The
container does this. You just provide appropriately-named abstract get/set
functions. In fact, the implementation class of a CMP entity bean should be
abstract in EJB 2.0.
This is all great. But what I would like to ask is, will the use of
old-style explicit CMP fields be deprecated when Jonas supports EJB 2.0? Or
will we have to recode all our CMP entity beans to fit the new model? I
would most definitely vote for the former! (i.e. deprecation).
Joe
=====================================================================
Joe Gittings, Royal Botanic Gardens, Kew
Hanover House, Kew, Richmond, Surrey TW9 3AB
[EMAIL PROTECTED]
+44 20 8332 5712
fax: +44 20 8332 5736
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
