Thanks for the info about Merlin. I'm looking through the docs now and will download and play with the demo as well. I'm not using the context lifecycle, but I think I could really use the dependencies that you mention.
One problem I have right now is that if one of my components does not configure properly, I have no real way of 'knowing' this from other components or the container. I'm using 4 components right now and they are all interdependent at some level. In a nutshell what would be nice is that if a component does not configure the container/service manager, etc would know about and not allow it to be active. This might break a few rules and from what I know right now, there is no callback from the component to say "I'm not ready/configured". - Robert -----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 12:17 PM To: Avalon Developers List Subject: Re: Migrating from ECM Robert wrote: >I have been planning on moving our product off of ECM since it isn't the >preferred container anymore (?), and was wondering which one should I go >to. I don't think I need phoenix as the container needs to lightweight >enough to run in a single, fat-client environment, so I think either >Fortress or Merlin would be my choices. So, with that in mind: > >- Which one is closer to production ready > Merlin is under active development - but its already running compoenents really nicely, providing: (a) the component is thred-safe (b) the component does not declare a context dependecy (that still in progress) (c) the component does not declare a default configfuration (that's also in progess) My guess is that the real question concerns point (a) because ECM compoents don;t know about default configuration or dependecies. The excalibur/assembly package contains several example compoents with Merlin doing the automated dependency resolution and lifecycle management - take a look at the demo and see if this fits with your needs. After a couple of other priority items I would like to focus on Fortress/ECM style handler integration for pooled components but thats at least three bullet points down the list. >- I need configuration as easy as, or close to as easy, as ECM was > I'm confident you will find Merlin configuration easier than enything else in Avalon. >- I am currently using the connection pooling from Excalibur and would >like to continue using it. > >Any thoughts? > > If you want to trial Merlin 2.0 (excalibur/assembly) post me an emil off-line and I'll try to help you with the job of getting things running. In the meantime, the javadoc for Merlin 2 is really solid - it will giove you a reasonably good picture of what is possible today and what is in the pipeline. Cheers, Steve. >Thanks, >Robert >- > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- 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]>
