Thorsten Scherler wrote:
Hello devs,
I am developing some usecases for a lenya pub based on 1.4.x. The
problem that I run into is that I added a new usecase to the one I
already had. After a couple of rebuilds and checking the code I finally
made a "build clean" and the second usecase showed up.
After looking again in the docu and in my code I found the reason why I
had to "build clean" (taken from default pub):
<xconf xpath="/cocoon/usecases"
unless="/cocoon/usecases/[EMAIL PROTECTED] =
'default/workflow.submit']"/>
The @unless prevent that we can add and activate new usecases unless we
do a "build clean". That is because we have a dependency on *one*
usecase "/cocoon/usecases/[EMAIL PROTECTED] =
'default/workflow.submit']".
Do I understand that right?
Looks like a copy&paste error. The "unless" attribute should point
to the usecase you want to insert. It just avoids duplicate entries.
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.
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.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
