Thorsten Scherler wrote:
[...]
Hmm, the default pub has more then *one* usecase in the usecase.xconf.
Would it make sense to have something like this:
usecase-workflow-submit.xconf
usecase-my-usecase.xconf
...
That would bring back the behavior you describe "It just avoids
duplicate entries".
wdyt?
That would be possible, but is it really worth it?
We end up with a lot of files when the number of usecases rises.
How can we overcome that problem because a build clean is IMO not
necessary.
During development, you could add a "remove" attribute instead of the
"unless" attribute. Then the snippet is just replaced during patching.
Yes and no. The @remove will remove *only* the usecase of the xpath
expression but not all usecases that are stored in the usecase.xconf (if
it contains more then one usecase - like the default pub).
That *will* lead to duplication after the second build.
OK, when you add more than 1 usecase that's true.
But in production, you can't do that because cocoon.xconf will be
changed during every build process, which requires to restart the
servlet engine.
That is perfectly alright with me but I do not want to be forced to do a
build clean.
OK
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
