Richard Wallace wrote:
Hello all,Within an embedded environment the bootstrap package isn't necessary - in effect you would simply instantiate a new block. There are not example of this yet (but its comming). I'm not totally happy with the bootstrap process at this stage and I would like to do put some more effort into making the initial command line deployment a more brain-dead exercise.
I'm creating a webapp and would like to embed merlin. I'm using the
avalon-sandbox version because our planned date of deployment is 3-4
months, right around the time the next merlin release is planned.
I've looked over the Merlin.java file in the bootstrap directory. I'm
wondering how much of that code is necessary is necessary or if someone
has maybe already put some effort into doing this.
Aside from that - you should look at the test cases in the assembly package. If the number of components and depedencies are relatively static then you don;t need Merlin - the assembly package provides everything you need to deploy a component. On the other hand, if you applying auto-assembly agaisnt unknown content - then you want Merlin because it adds more management over and above the assembly package.
On the web server side - I've been using Tomcat successfull within Merlin (and Merlin within Tomcat) for doing things like dynamic navigation of containers and components. The Merlin 2.0 to 2.1 transition will make it much easier to package things like a web-server into a single deployment unit but there is some refactoring to be done first. Anyway - the objective is to arrive at a situation where is a good solid solution for the following applications:
* security (access policy in meta that is resolved relative to a principal)
* distribution (conecting containers over IIOP - including propergation of principal)
* administration (desktop management for the assembler/administrator)
* registration and discovery (locating, and deploying/referencing compoents/services)
* auditing (storage and notificatioin of events)
* gateways (web-service and electronic messaging services)
Just about all of the above is in place in one form or another - some in open-source, some over on osm.net. Once Merlin/Assemble/etc. is released there is the general process of container convergence with Fortress, Phoenix etc. In parreallel I would like to see the above functionality moving to open-source (preferably here).
Things like theThe classloading is important because this is where the assembly package identifies that there is a candidate component type. I.e. jars containing component types need to pass through the EngineClassLoader scanning process which results in the establishment of the type, service, and profile (template) repositories. Based on that - the Merlin system can do the auto composition.
properties and the paths can be configured in the web.xml file so those
utility methods to get that stuff isn't necessary. How about the stuff
to setup the classloaders?
Let me know what you application scenario is - I have some thoughts about other things going on here or at osm.net.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
