Peter Donald wrote:
Hi,
I like the idea but can we let it incubate for a bit. There is large number of changes that are currently going on in Apache. I think we will find that large chunks of Avalon will move to either the incubator.apache.org or commons.apache.org projects. In both of these cases it will just take time.
I agree - but I do think discussion outside of Avalon is good thing.
In some of these cases the specific components when they move may also take some of the Avalon services. ie Currently Extension is void of references to Avalon, it may be that we migrate the service back from Phoenix into Extension toolkit when it moves to commons.apache.org. So in this case it may be best to instead have a registry of services for Avalon and allow people to pick them up from different places as they desire.
Makes sence.
There is also the problem of interoperability. Not all the components are interoperable. Some are restricted to Phoenix, some are restricted to Cocoons ECM/Fortress managers and some are generic. Some will also presumably be specific to Turbines container.... one of the interesting things about specifics is establishing why a container specific feature is needed. In some cases its a container extension but in other cases its a question more related to the component model itself and need to provide richer functionality. An example of this is the extensions mechanism available in Fortreee and Merlin. Other examples (closer to things I'm dealing with today are the differences between component implementations that can be defined statically versus components whose services are a function of their configuration, or deployment). These are the sort of things that are extractable from "non-portable" components and collectively establish requirements that Avalon should be looking at in terms of the framework's development.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
