James-HA provides two custom repositories DistributedJDBCMailRepository.jav and DistributedJDBCSpoolRepository.java which extend JDBCMailRepository and JDBCSpoolRepository, respectively. Instead of using o.a.j.util.Lock, they use the distributed lock.
A better way to do it would be to extract an interface from o.a.j.util.Lock and tell the existing repositories which lock to use. If you don't want clustering, use the local lock. If you do want clustering, use the distributed lock. The idea is that the lock itself would be configurable. This is the way I wanted to do it originally but I didn't want to muck around with the Avalon cruft . If someone is willing to do the Avalon configuration leg work, I'll get the distributed lock stuff polished up and in a state that it can go into James. -Mike On Tue, 2005-06-07 at 14:51 -0400, Noel J. Bergman wrote: > Mike, > > OK, what is the current state of James-HA? How does it integrate into > JAMES? What do we need to do to integrate that as an optional capability in > the main distribution? Are you willing to do that work? > > An overview and then coverage of the integration points would be good for > everyone. :-) > > --- Noel > > > --------------------------------------------------------------------- > 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]
