Pardon my ignorance on Struts as I haven't used it extensively either, but my recollection is that Struts invokes Actions which then return a forward - in essence telling the controller what to do next based upon what the business logic for the action did. This, in essence and IMO, makes the Action more knowledgeable than it should be.
Cocoon's notion of an action is somewhat different, although it can be subverted to behave very similarly to a Struts action. Typically actions in Cocoon simply return information in a Map object. The pipeline is configured to operate upon that data in any manner it sees fit. Thus, the action is in the business of simply returning information rather than acting as a director. Ralph -----Original Message----- From: Derek Hohls [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 8:57 AM To: [EMAIL PROTECTED] Subject: Re: new to cocoon question Interesting question - in brief, actions are primarily used *inside* pipelines to act as logic "switches" between different choices; or to allow easy handling of case failures. I am not sure how this corresponds to what Struts does - I actually would like to find out more about Struts as there a number of developers I know that use it, to whom I'd like to relate a little better - if there is any reading you can point me towards to grasp that framework's approaches, I'd be happy to share any comparisons I find (as this is something I want to do anyway...) Derek D Hohls Environmental Systems Developer CSIR Environmentek PO Box 17001 Kwa-Zulu Natal South Africa 4013 www.csir.co.za --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
