I'm new to some of these concepts, but here's my feedback:
1. Whether you use BMP or CMP depends on the complexity of your EJB AND the
limitations
of your container (e.g. supporting data across multiple tables).
2. Always use ejbLoad (and any other ejb<???>) method when it comes to
persistient. That is
the nature of the standard AND containers reply on your compliance.
I have not dealt with transactions so I cannot comment on the third
question.
Leon
-----Original Message-----
From: Nikolaus Rumm [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 20, 2000 2:47 PM
To: [EMAIL PROTECTED]
Subject: Design questions on dependent objects
Hello,
my questions are regarding dependent objects (persistent, fine grained java
objects (not entity beans) that depend on an entity bean).
I am looking for some "best practices".
* Is it recommended to use BMP or CMP entity beans for persisting dependent
objects ?
* Is it better to persist the dependent objects in the ejbLoad/ejbStore or
in the set/get methods of the bean ?
* How do I add the persistent objects to the transactional context of the
entity bean ? The case is clear if the bean is part of a transaction and the
isolation level is some kind of "write block", and thus the dependent
objects are not accessible for write access to non transaction members, but
what for optimistic locking ? Should I implement some kind of dirty flag
mechanism in my dependent objects ?
Any help would be appreciated
Nikolaus
===========================================================================
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".
