Joe, I am including a list of things from the top of my head that I like about Cocoon sitemaps, and how it translates into struts-chain. I would like to say that maybe this is a great area for cross-pollination. Why reinvent the wheel? Perhaps a commons package shared by the Cocoon developers and Struts developers for these webapp request processor configurations. On the other hand maybe it is too late for this type of activity? Anyway, here it goes:
1) The ability to declare variables that can be used throughout all chains (e.g. a variable defining a root jndi context name). The variable could be used in the chain to affect very basic flow. The variable also could be passed into the Command objects. 2) A reload attribute on the entire chain config or may be individual chains. This would enable faster development...if the config is changed, it is visible without a servlet container restart. 3) Chain definitions bound to a variable name (I believe Craig proposed this). This would be similar to Cocoon's cocoon.xconf's input/output modules in the WEB-INF dir: <component-instance class="org.apache.cocoon.components.modules.input.RequestParameterModule" logger="core.modules.input" name="request-param"/> This particular snippet binds the string "request-param" to an object that allows one to access the request object of the servlet container...e.g. request-param:userID 4) URI protocol handling for initializing, pulling sources from, or redirecting to other chains. Similar to Cocoon's "cocoon:/" and "cocoon://" protocols. >From Cocoon's site: context:// - get a resource using the servlet context cocoon:/ - get a pipeline from the current sitemap cocoon:// - get a pipeline using the root sitemap resource:// - get a resource from the context classloader Well I think it is clear by now that I really like some of the Cocoon architecture ;). Anyway, I think the Cocoon sitemap paradigm is a developer's dream and nightmare at once. The dream is the URI handling with regex matching, sub-sitemaps, and the array of generators, transformers, and serializers. However, the nightmare is the learning curve and the bloat. I hope that by writing this email...this newbie can translate some Cocoon experience into something valuable for all. regards, Julian p.s. some resources http://cocoon.apache.org/2.1/userdocs/concepts/index.html http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
