On Wed, 8 Aug 2001 19:34, 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.
Ouch! I guess Avalon could be used to do something like that along with a XML/XSLT tool to create bindings however its a huge amount of work. Have you looked at the JDO specification from JCP? I looked at it for a bit and it seemed mostly good (didn't play nice with distributed transactions though IIRC). Anyways if you decide to implement it yourself goodluck - you are going to need it - I wenth through the pain of binding objects to network protocols and know how irritating the bugs in those setups can be ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
