On Apr 24, 2004, at 5:30 PM, David Sean Taylor wrote:
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.
This is exactly what I prefer to do.
Or at least make it configurable.
It is. The entertaining part comes in when you combine caching, as soon as you have something modifying the database which does not take part in the cache system you cannot use the cache. Per-broker caching is, generally, the only acceptable cache for any large installation
What is the OJB solution when you have more than one machine running on the same OJB network of objects?
If they are both using OJB you can use a distributed cache and distributed lock manager, or optimistic transactions. The most performant distributed lock manager is the LockServer, which Thomas M. hasn't really documented yet =( You can also lock via mutexes in database.
If you are using the PB API you need cannot get object-level transactions anyway, so the database transaction and a distributed cache (or more often a per-broker cache) will have to do. Always (this applies to any O/R mapper, including Hibernate) re-obtain object references inside a new transaction if you care about transactional integrity =)
Personally, I haven't had a case where optimistic transactions haven't been acceptable, and this is generally much preferred as it scales much more nicely.
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?
Thank you!
-Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
