I wrote:

<snip/>
Just Do It already!

Putting my money where my mouth is....


....some more docs now up at

http://lsd.student.utwente.nl/jicarilla/

and some code up at sourceforge. I think code is now of a level that allows me to say "we can make it work if we want it to work". Among the features is (provided things actually work as I couldn't be bothered to write tests for what is basically mock code) full support for Pico-style, XWork-style, and Avalon-style components, as well as a mixture of those and some extra options as well.

Also implemented are the ComponentFactory idea (as per pico and Berin's latest RTs) though I just called 'em Factory, AOP-style interceptors (very basic; a realistic implementation might be nanning-based) using jdk proxying, and I put in the start of jython-based scriptable components.

There's a nice mix of simplicity and possibility imho though the default dependency management stuff might need to be beefed up, ComponentDescriptions expanded and everything rewritten from scratch just for the fun of it.

---
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/jicarilla login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/jicarilla co jicarilla-sandbox


cd jicarilla-sandbox/platform
cd components/collections
maven
cd ../../framework
maven
cd ../container
maven
---

Don't bother looking at the "collections" or "framework" stuff, that's not actually used (you just needed the CascadingExceptions 'n stuff from framework, and framework depends on collections).

Fire up the class DemoMain in your debugger to get to grips with the package. Important difference between this package and our existing containers is that the assumption is not that the container will ever read any config files, rather there will be a layer around the container (call it kernel if you want) that does that. See the JicarillaWiki for some sketches.

Do you guys consider it worthwile to start working on a setup like this over here @ avalon?

cheers,

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to