> 1) Who defines dependent *value classes*? The bean provider or the PM?
Bean provider. These value classes can be used by the clients of the
bean to pass the data to the bean to initialize, create or modify dependent
Objects. Since dependent objects are non-serializable, the data for
dependent objects can be passed through these dependent value classes from
the client.
> 2) If the bean provider defines them, then how does the PM know how to
> persist dependent value classes? You are not defining them in the DD
> (9.4.9).
Only bean provider has the knowledge about them. These value classes
are sort of data objects.
> 3) Can dependent objects or PM-provided collections be marshaled to
clients
> that are also EJB components running within the same container?
PM-provided Collections cannot be exposed to the clients (other
beans etc.)
> 4) If we access a CMP dependent object from a BMP entity bean, how does
one
> define the required create() method on the BMP entity bean?
Only CMP bean can be associated with dependent Objects. So you cant
have create<> for dependent objects in BMP.
> 5) What is the point in defining a set accessor for a primary key field?
All the CMP-fields are set using set-accessor methods. For PK,
it is a one time job. EJB2.0 allows bean provider to expose getter and
setter methods for CMP-fields. But care must be taken not to expose
set<method> for PK. (in public final draft of EJB2.0) See Section : 9.4.1
for usage of set<method> for PK field, and see section 9.4.11 foe details of
what all can be exposed to client.
> 6) Section 9.5.3.1: Why does the PM have to persist homes?
>
> Thanks
> -Ed
Regards
Hemant
Pramati Technologies.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
