> Also they want to know how much of the effort of setting up a cocoon can be > reused if we decide not to go with cocoon. I suppose the business logic can > be reused and possible the stylesheets but I am not sure.
If you stay away from XSP then much of what you do can be reused. If you're careful all your XSLT are portable. Similarly, Cocoon is a big servlet: if you're careful (extend a common base class that of your own) actions and generators can be maybe 80% reusable, though you'll have to write a lot of code to move them anywhere: Basically, you'd have to implement your own servlet that probably made hard coded assumptions about resource names. It would call your generators to pass the output on to an XML transform. From there you'd call your actions, again with a bunch of stuff hard coded. I can't imagine actually wanting to ever do this, but much of our code has been written with this possibility in mind. Now that Cocoon is more accepted here this requirement may go away for us in the future :-) --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
