1. what version of javaflow?
2. what version of jci?
We're working with the trunk version : 1.0-SNAPSHOT for jci-core and
javaflow
Then we tried to integrate the FilesystemAlterationMonitor with the
cocoon classloader configuration, in order to automatically reload
and enhance the Javaflows when changed, but we faced with some problems.
- The FilesystemAlterationMonitor always notifies the changes of
those classes that are enhanced; the check is based on
file.getLastModified() value, but every time the value is lower then
the last one, so the change notification is triggered. We didn't
investigate more.
The FAM should notify about all classes once after the startup
...after that it should work fine. A few problems under Windows have
been reported though. (including suggestions on how to fix it)
What OS are you testing on?
Gentoo Linux - FS ext3.
Maybe the problem is that first time it reads the original bytecode, so
it enhance it and writes the new bytecode; since the class has changed
the second step will notify it, triggering another transformation, and
so on. We should transform all the classes once and then run the FAM.
I'll do more tests on it.
We can also provide our temporary changes to the javaflow poms in
order to enhance the JavaInterpreter and the javaflow classes at
build time, using the RewriteAntTask provided by commons-javaflow and
some fix to the cocoon-javaflow-sample block.
Wait a sec ....you don't want to instrument the JavaInterpreter! But
enhancing classes at build time is a nice addition.
Yes it's true. Sorry for the mistake; we instrument the following classes:
Invoker.class
FormInstance.class
AbstractContinuable.class
VarMap.class
Maurizio
