> Stefan: > > I think this may be the wrong approach. Instead of modifying the > sources as your suggesting, I think the better approach is to > either (a) > modify the tools that are generating meta-info for Fortress, or (b) > modify Fortress to recognize meta-info via the Avalon Meta framework. > > Stephen.
Even better, but i'm not sure what your further plans concering fortress and meta framework are: - Is ist planned to switch fortress to the new meta framework once it is ready? In this case it makes not much sense enhacing the forrest meta-info generation. - Is the avalon meta framework ready for broadening its scope beyond the merlin container? (i must admit that i did not have a deeper look into the current releases) - Is there a reason why fortress uses a different way to collect the meta-informations? Or is it just historical evolution? - Is there already meta information defined based on avalon meta for the cornerstone components or plans to do so? - Is Fortress replacable by merlin? From the documentation i got that merlin is the sucessor of phoenix, but not suited for a embedded servlet environment like fortress. Is this correct? Or was this already discussed on the mailing list? I searched a bit but found not much concerning fortress and cornerstone. If i know your plans i can see where i can help. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
