Sounds similar to Enterprise Object Broker server (which is phoenix-based),
actually, I was thinkong about on including that in the package :D. EOB will be pico-based in v2, but nevertheless there should be no more than a simple wrapper neccessary.......and EOB is way cool.
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?
hmm. I think there's a difference between assembling stuff (hosting only the scripts that take care of the assembly) and actually hosting the stuff. The difference is in the amount of stuff the PMC has to take responsibility for. Still, perhaps the easiest approach is to set up a sourceforge project for this. Among other things, it'll allow the use of LPGL components.
- 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.
indeed! I was thinking last night about a little python script that parses something like:
blocks.py
---------
class eob:
name = "Enterprise Object Broker"
version = "2.0b1"
bindist = "http://www.enterpriseobjectbroker.org/bindist.zip";
srcdist = "http://www.enterpriseobjectbroker.org/srcdist.zip";
javasrc = ("src/java")
jars = ("jars/eob.jar",
"http://avalon.apache.org/tubfad/mods/eob-mod.jar";)
license = "LICENSE.txt"class mx4j:
name = "mx4j"
version = "1.1"
bindist = "http://www.mx4j.org/path/to/bindist.zip";
srcdist = "http://www.mx4j.org/path/to/srcdist.zip";
javasrc = ("src/java", "src/etc")
jars = ("mx4j.jar",
"http://avalon.apache.org/tubfad/mods/mx4j-mod.jar";)
license = "LICENSE.txt"(etc etc)
downloads all the distributions, unzips them, copies the files from the appropriate locations, retrieves any needed patches, builds the javadocs, etc etc. Of course, other options include a maven plugin, reuse of an installer package like cygwin uses, and more.
I'm not up to speed on the latest merlin capabilities, but I think the merlin block model doesn't currently address the ability to specify where sourcecode or licenses (etc etc) live, but these are things we want to include as well. Of course, the block model could be modified.
Alternatively, you could also create a 'pre-installed' merlin distribution that already has all the resources loaded.
This is probably simpler to do at first, but possibly a lot harder to maintain.
- 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)
I think we'd be willing to have that stuff hosted around here :D
- How does this relate to other similar projects, both in Apache and out? IE- Geronimo, EOB, JBoss, ...
geronimo is (at least for now) not going the avalon route. EOB is 'just' a business object service (ie the EJB part of the J2EE stack, only better), JBoss will also keep doing their own thing.
So it could be seen as indirect competition, I think :D
cheers!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
