> -----Original Message----- > From: Leo Simons [mailto:[EMAIL PROTECTED] > Sent: Monday, September 22, 2003 4:48 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [RT] The Much-Needed Kitchen Sink Distribution > > Hi gang, > > an idea that first came into being in the Phoenix Development Kit (PDK) > that we never quite finished. Lean and mean is a good idea in general, > but as a demonstration of power, features, and an actual setup a > "kitchen sink distro" can be very useful as well. > > I've raised the idea several times before. Lets see if the spark can > gather the critical mass required to start the lightning strike :D. I'm > not going build this thing, but I can help to set some basic things up > if there's enough interest. Responses to the development list please. > > - Leo
+10000 Sounds similar to Enterprise Object Broker server (which is phoenix-based), but having something like this out of the box from Avalon would be cool. If nothing else, it would be a nice way to 'show off' Avalon. More Random Thoughts: - This somewhat flies in the face of the "The Avalon project is about the framework, not the applications" focus which I've seen. How big of an issue is that? - There's lots of ways to do this with merlin. Various distributions could just be various 'block.xml' files, plus perhaps some local config files. In otherwords: 1. Download + Install Merlin 2. Download this small zip which defines Avalon Distribution flavor 'A' 3. run merlin.sh/bat on the included block.xml 4. Downloads resources from appropriate repositories. Advantages: We wouldn't have to host third party jars on avalon, just point to the third-party repository. This gets us around some licensing issues I would think. Alternatively, you could also create a 'pre-installed' merlin distribution that already has all the resources loaded. - An 'Avalon Development Environment' would be nice. I've thought about putting together a set of Eclipse plugins that would help with Avalon component development, assembly, and deployment. This is a large project that's only a pipedream now and perhaps more appropriate outside of Avalon (don't know yet) - So Avalon Project would have the following 'products'(?): - Framework : The core Avalon framework itself - Fortress : small, simple, embeddable Avalon 4 container - Merlin : Full-featured Avalon Service Platform (replaces Phoenix?) - Components: Cornerstone + Excalibur = basic core components - "TUBFAD" : the prebuilt Avalon Distribution - How does this relate to other similar projects, both in Apache and out? IE- Geronimo, EOB, JBoss, ... You've at least sparked my interest. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
