On Apr 23, 2004, at 5:29 PM, Brian McCallister wrote:
Some odd errors. Let me grab JetSpeed head and nose around.Why not let the database handle the cascade deletes?
OTM is definitely an unstable piece of code right now. It provides a lot of really nice functionality but is... young.
cascade delete (auto delete) changed some in RC6, old expected behavior should be preserved to my understanding, but I don't often use PB level cascades.
Or at least make it configurable.
I personally prefer having the database handle integrity constraints
What is the OJB solution when you have more than one machine running on the same OJB network of objects?
At least the error messages and examples aren't all in German ;-)Look at components/registry and components/persistence for starters
Seriously, will grab head and nose. Any pointers to where in your source tree your persistent objects, and code that controls their persistence is hidden?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
