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
cocoon/WEB-INF/classes or cocoon/WEB-INF/libs (for jar files)
-Andy
Robert Bourdeau wrote:
I think there was a thread on this, BUT it appears that the
cocoon-users archive is not indexed, there is no web archive, and
I can't keep all the Cocoon-user messages. So, apologies in advance
if this
Robert Bourdeau wrote:
I think there was a thread on this, BUT it appears that the
cocoon-users archive is not indexed, there is no web archive, and
I can't keep all the Cocoon-user messages.
http://marc.theaimsgroup.com/?l=xml-cocoon-users
That's pretty unsatisfying.
I just disentangled my Tomcat 3.x JSP apps from each other when upgrading
to Tomcat 4, localizing their WEB-INF dirs to allow them to be evolved independently.
Now, with Cocoon, I'm back to a single WEB-INF? Not a good solution.
I found a message from Vadim in the
From: Robert Bourdeau [mailto:[EMAIL PROTECTED]]
That's pretty unsatisfying.
I just disentangled my Tomcat 3.x JSP apps from each other when
upgrading to Tomcat 4, localizing their WEB-INF dirs to allow
them to be evolved independently.
Now, with Cocoon, I'm back to a single WEB-INF? Not
It's not that these solutions won't work, but they feel awkward and
seem a little like hacks. I work in a shop where we have multiple
virtual hosts running on a single server configuration, and within
each virtual host, multiple applications. Further, there are dev,
alpha, beta, and
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
You still can keep your concept of Application. I look at Cocoon as a
framework, within which my applications run. I make each application a
subdirectory off the main directory, and each has its own sitemap. The
benefit is that I have a clean sitemap, (i.e. very few map:component
definitions
From: Robert Bourdeau [mailto:[EMAIL PROTECTED]]
It's not that these solutions won't work, but they feel awkward
and
seem a little like hacks. I work in a shop where we have multiple
virtual hosts running on a single server configuration, and within
each virtual host, multiple
