Hi Lars,
On Jun 21, 2005, at 3:13 PM, Lars Huttar wrote:
Dear Cocoon-based webapp developers,
I would be interested to hear how others have handled this issue.
You have Cocoon applications whose source code is stored in a
repository. You want to be able to install them on multiple
development machines (on each developer's desktop), on test servers,
and on production servers.
The environments (dev, test, production) use separate database servers
as well as separate web servers.
But when you checkout the source code from the repository onto various
web servers, they're all pointing to the same database server, because
they all have the same datasources defined in cocoon.xconf.
You could then go in and modify cocoon.xconf separately for each
environment, but that could get to be a lot of time-consuming and
error-prone work. (We currently have 38 datasources defined for all
our applications! Maybe not all of them are still used, but most are,
I believe.)
How do you automate this task?
With the xpatch Ant task, included with Cocoon (the cocoon build uses
it). See http://wiki.apache.org/cocoon/XPatchTaskUsage.
HTH,
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
