Hi there, I am being using Merlin now for three weeks. I started to setup the first projects.
. I think one of the nice things that start to change for me is thinking in components and interfaces (APIs). I've got now an application, a resource manager api and impl, and a splash screen api and impl working (5 projects, 3 containers, 2 APIs). . Other nice things is being able to configure and overwrite configuration, to have a parametrized context and a lifecycle. Merlin does load configurations, component descriptors and invokes the different lifecycle stages for me. However, before Merlin, we basically had similar things. The configuration was not that sophisticated and lifecycle not abstracted. For me thinking in interfaces is one of the main merits while I have dealt with and thought about Merlin. I am starting now extracting a common project which should incorporate some utility classes that are used by a lot of other projects, basically static methods or singletons. Once again I am asking myself, what are the main criterias to decide whether to incorporate a new library as an own component or as a usual library in the lib directory. I could also make dependent projects that build their jars into a common lib directory so that each component loads its dependent jars from that.I sometimes think that I have missed some important point about Merlin. I would appreciate to hear some opinions about that: What are the advantages of Merlin (apart from what I mentioned above)? Is there some kind of distributed computing ability (like CORBA or WebServices)? Sometimes I have to reconsider what I am doing here. Thanks for your time Daniel Frey --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
