I'm currently exploring the possibilities for implementing a cocoon-inspired web-application framework without the complexity of XML processing (simplified sitemap that controls process flow from generators to serializers, no transformers, just support for aggregation/inclusion and pluggable template engines). And I'm looking into ways of using Fortress for that purpose. However, if I want to use subsitemaps with their own definition of components that can override parent sitemap's component definitions, how should/would I implement that? The natural way seems to be to use nested service managers, right?
Then the next natural question is: how to proceed? Use fortress.role.impl.lookup.FortressServiceManager/fortress.role.impl.DefaultContainer? Use framework.service.DefaultServiceManager? I guess the answer boils down to the question, how do I want to configure it... let's say that I will have the configuration data in the same format as the usual fortress configuration. what is the recommended way?
Rgds, Neeme
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
