Hunsberger, Peter wrote: >> Now, yes, I could create subdirs in cocoon/WEB-INF/classes or create >>separate jars for each in the libs, and have my apps each include their own. >> >>The other possibility is deploying Cocoon multiple times as different EARs, >>once for each "application". That way if one application needs some >>features of a particular Cocoon release that breaks other things you're >>still fine. >> This seems like a good solution for the multiple developers / projects / releases situation. One project could use Cocoon 2.1, while another could have already stabilized with 1.8. You lose some caching and pooling opportunities across "applications" but the gain in scalability and modularity could well be worth it.
Ryan Hoegg ISIS Networks --------------------------------------------------------------------- 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]>
