The "hasReloaded" notification should
happen after the compilation has finished and your classes
should be available after that.
As I wrote above the first "hasReloaded" happens already by the
CCL itself at
the end of its start() method. The second "hasReloaded" is the one
to go at the
mo
The "hasReloaded" notification should
happen after the compilation has finished and your classes
should be available after that.
As I wrote above the first "hasReloaded" happens already by the CCL
itself at
the end of its start() method. The second "hasReloaded" is the one
to go at the
m
Torsten Curdt apache.org> writes:
> > I have a problem with loading a class immediately after the setup
> > of the CompilingClassLoader. With a setup like in the TestCases using a
> > signal object it does not work (I get ClassNotFoundException), because the
> > CCL does release a reload() ev
I have a problem with loading a class immediately after the setup
of the
CompilingClassLoader. With a setup like in the TestCases using a
signal object
it does not work (I get ClassNotFoundException), because the CCL
does release a
reload() event immediately after setup - before my files have
Hello,
I have a problem with loading a class immediately after the setup of the
CompilingClassLoader. With a setup like in the TestCases using a signal object
it does not work (I get ClassNotFoundException), because the CCL does release a
reload() event immediately after setup - before my files ha
