>>4.) Proceed in "baby steps" when changing things in your cocoon app > > But it really slows up development
Doing incremental development will ultimately save you many many, days of lost productivity. The biggest roadblock is having sufficiently powerful hardware that doing many compiles and redeploying Cocoon doesn't cost you a lot of time. Splurging for the best hardware you can afford will likely pay itself back very quickly in time savings... For XSLT changes it's usually simple to proceed in baby steps since you can usually edit the live sheets and resubmit the page and immediately see the results. In addition you can break your pipelines into pieces so that you can capture the output XML and feed it into something like XML Spy or Xselerator and debug your XSLT that way. --------------------------------------------------------------------- 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]>
