On Dec 3, 2006, at 4:50 AM, Gabriele Columbro wrote:
Hi Mark (Maurizio is here on my side not answering due to annoying
mail server issues)
bummer :-/
and we're working on reloading classloader configuration.
You're right, the TreeProcessor already behaves like this, by checking
the value of
org.apache.cocoon.reloading=[yes,no]
right...
used also to control sitemap reloading. You can then easily configure
this value differently in the different modes, e.g. dev mode uses
'yes'.
right...
We preferred not to add yet another property since the class reloading
functionality is about a very similar concern (actually reloading is
pretty generic).
+1.
So, I misunderstood Maurizio's comment, you are not using the mode
directly but using o.a.c.reloading? I didn't see any reference to it
in the patch files (but I didn't see any reference to o.a.c.mode,
either). I did spot a typo :-)...
"cocoon-bootstrap-realoding-classloader-factory.xconf"
Is this what you meant?
Yes.
As side note, did you already try the reloading classloader sample,
which you can reach at [1], running cocoon-dist-samples block ?
Not yet, but I will! :-) Thanks a lot for this.
—ml—
