Hi Eric,
I'm unhappy to point out that this could happen in theory - but I propose something different. The real problem reusing an Avalon component across multiple containers (apart from a dependency avalanche) is the container-specific naming of the context entries. It is hard to understand how this had happened but it is a reality - in German we would say "they had a bad day".
What I check out in January is to add "containerPersonality" to the RoleConfiguration.xml which defaults to "merlin" - this is the "urn" stuff. For "fortress" or "phoenix" I can setup a proper context. It should be feasable to write an Excalibur test container and proof that existing Excalibur components can be used with YAAFI (they have a nice SourceResolver component )
What I don't want to do is
+) to create a Phoenix-Testcontainer - working with JAMES and Phoenix drove me insane but I succeeded in adding YAAFI as component into JAMES . This is basically another way of tackling container incompatibility - just embedded the container as a component into an Avalon container which works well with YAAFI since only one JAR is required.
+) to integrate Phoenix services since I want to focus on existing Jakarta projects
Thanks in advance
Siegfried Goeschl
Eric Pugh wrote:
CC'ing this to Turbine -dev as well.
YAAFI stands for Yet Another Avalon Framework Implmentation and was created to provide a very simple container with minimal dependencies that still fulfilled the Avalon Framework contract.
I think that adding support for some sort of compatibility test suite is crucial to validate that the components really are cross platform. To some extent, that is set up through the current BaseUnitTest in Fulcrum-Testcontainer's support for either ECM or YAAFI. By default it uses Yaafi, but flip a switch and it uses ECM. Adding a Fortress support would be great. Theorectically, then, any unit test that extended BaseUnitTest could pick which container was used.
What I hope doesn't happen is that by adding another container we start having to customize each component per container it runs in.....
Eric
-----Original Message----- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: Monday, December 13, 2004 1:20 PM To: Excalibur Developers List; Eric Pugh Subject: Re: A few thoughts about Avalon, Excalibur and future Avalon comp onents ...
Hi Aaron,
a lovely list - I was not aware that so much stuff is out there ... :-)
I think that Fulcrum does not use Fortress for testing container compatibilty - only ECM, Merlin support was removed recently. And yes, Fulcrum has currently its one Avalon Test Container called YAAFI ... ;-)
What I would like to do is to set up a compatibilty test suite for the existing Fulcrum codebase using ECM, Fortess and YAAFI - basically ensure that the current services runs on the containers hosted on Jakarta ( Eric - your opinion about adding a Fortess test container?!). Well, ECM and YAAFI is already in place ....
Cheers,
Siegfried Goeschl
Farr, Aaron wrote:
-----Original Message----- From: Marcus Crafter [mailto:[EMAIL PROTECTED]
I'd be +1 to add some external links to the Excalibur website pointing poeple to the other services available.
Gang, what do you think?
+1
I used to have a really nice list on Avalon before the new site launched. You can find most of it on the wiki at:
http://wiki.apache.org/avalon/ProjectsUsingAvalon http://wiki.apache.org/avalon/AvalonComponentDirectory http://wiki.apache.org/avalon/AvalonRelatedProjects
Also, we should look at making an "Excalibur Powered" logo and specifying how it can be used.
jaaron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
