On Wed, Aug 08, 2001 at 11:34:06AM +0200, Michael Bachran wrote:
> > -----Original Message-----
> > From: Peter Donald [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, August 08, 2001 10:01 AM
> > To: Avalon Development
> > Subject: Re: avalon and soap (+ JMS + JNDI)
> >
> >
> > On Wed, 8 Aug 2001 17:38, Michael Bachran wrote:
> > > What about a locking mechanism in Avalon? Can it be imlemented
> > based of an
> > > object pool?
> > > Or is there already one?
> >
> > Not sure what you mean exactly ;)
> > Avalon/Excalibur has a Component pool and has separate locks (in
> > concurrent
> > package) but I don't think thats what you are getting at?
> >
>
> I want to handle metadata independent from the persistence system like
> rdbms, odbms or xml-files (that should be interchangable). Therefore
> basically the metadat is represented by java classes/instances I need to
> work on concurrently doing internal locking and so on, combining that with
> clustering and load balancing of components (and maybe caching of metadata
> objects).
> I wonder how easily that can be done with Avalon. Seems to me that the
> concurrent package might help for the locking. I have to take a closer look
> at that.
Have you had a look at Castor (http://castor.exolab.org/)? It handles
object persistence to XML, LDAP, RDBMS, and necessarily has quite a
snazzy locking/transaction system. No doubt metadata plays quite a large
role.
--Jeff
>
> Ciao, Michael
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
