Hi Andrew, Lienhard, Andrew wrote:
apart from the C/S mode document shipped with documentation and the hints in OJB.properties you won't find much about this scenario.We're considering using OJB for a large web project this spring. We run about 5 servlet engines (Resin) in production. We're can I find documentation on how to configure OJB to run across mulitple machines for caching/locking?
Are you working against the PersistenceBroker API or against ODMG?I assume this is something that is configured in OJB.properties (LockMapClass ??). Are there any gotchas to consider? The app is for user management, so caching is not that critical.
Most servlet apps I know are using DAO pattern for data access. IMO the PersistenceBroker API fits the DAO approach much better than ODMG.
with PB things are pretty simple.
You can use optimistic locking (version- or timestamp based) to detect write conflicts.
You can use explicit calls to the PB API for cache management. (E.g a cache clear).
with ODMG things are a bit more complicated. If you want to have a proper transactional isolation across VM's you have to use the PersistentLockMapImpl to handle the lockmanagement accross VM's.
This is done in OJB.properties.
there should be no further caveats.
cheers,
Thomas
Thanks, Andrew Andrew Lienhard Web Technology Manager United Media 200 Madison Avenue, 4th Floor New York, NY 10016 http://www.comics.com http://www.dilbert.com http://www.snoopy.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
