Hi,
For applicators of Cocoon2; what is the recommended method for creating
multiple projects based on Cocoon? I currently create sibling project
folders to xml-cocoon2 and customize the projects build.xml to locate Cocoon
components and maintain a unique webapp folder for each project. There
On Wednesday 26 December 2001 09:33 am, you wrote:
For applicators of Cocoon2; what is the recommended method for creating
multiple projects based on Cocoon? I currently create sibling project
folders to xml-cocoon2 and customize the projects build.xml to locate
Cocoon components and maintain
26, 2001 9:48 AM
Subject: Re: Employing, maintaining, version upgrades
On Wednesday 26 December 2001 09:33 am, you wrote:
For applicators of Cocoon2; what is the recommended method for creating
multiple projects based on Cocoon? I currently create sibling project
folders to xml-cocoon2
-
From: Roger I Martin PhD [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 26, 2001 7:55 AM
Subject: Re: Employing, maintaining, version upgrades
Thanks, that was quick!
I'll apply your project source tree and be able to continue working this
week. The logkit.xconf was where I
On Wednesday 26 December 2001 01:00 pm, you wrote:
Wouldn't it be better to keep you xslt, xml (and all things that you don't
want or need the user to access) underneath WEB-INF? This way you keep
things more secure. Keep things like css or js (things that need to be
downloaded) in the
understand the entire procedure
regards
sumit
- Original Message -
From: Robert Koberg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 26, 2001 11:30 PM
Subject: Re: Employing, maintaining, version upgrades
hi,
Wouldn't it be better to keep you xslt, xml (and all things
