Julian:
In addition to the Chain Action, you can definitely configure a chain which dispatches to a sub-chain based on the request URI. The base chain is designed to provide backwards compatible behavior with existing Struts installations, but with a bit of adjustment, you can definitely break things wide open.
It's been a while since I looked at Cocoon, so the model, and especially the configuration for it is pretty vague. If you want to be more specific about what you're aiming for, maybe we can work out a config strategy. It will be a little raw now, but as people get ideas for best practices, we can gradually find ways to provide more explicit configuration support for them.
Joe
I was looking at the struts-chain config (http://cvs.apache.org/viewcvs.cgi/jakarta-struts/contrib/struts-chain/src/c onf/chain-config.xml?rev=1.10&view=markup) and was wondering if one can apply different chains depending on the request URI? From what is available in the SVN repository it looks like all requests go through the "servlet-standard" chain. This leads me to presume one cannot define "servlet-standardA", "servlet-standardB", and so on...that would map to different requests. My hopes is that the chain mapping would be synonymous with Cocoon's sitemap concepts with several "pipelines".
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
