Hi Leo, > since there might be more users like you (who wish to switch > from ECM to > phoenix), this could be valuable to them as it could easy migration > considerably...would you consider contributing your block?
I hope I will be allowed to. It would be an honour for me to contribute to this nice project. :-) > If that's doable for you, yep, that's really the general concept with > phoenix. (It basically comes down to granularity: phoenix > usually works > better on components that are more coarse than the components > typically > used in ECM systems.) But most big components are build out of smaller ones. And it would still be nice if one could administrate them all the same way (having to learn less, to search less meta data files, ...). Code reusage would be nice too, of course. So maybe one day there will be only one meta data parser, etc. for Avalon that can be scaled from a simple component manager up to a real container (e.g. Phoenix). Cheers, Ole -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
