Hi Geert,
How would you implement the first solution? I removed my source
directory as a source directory for IDEA while keeping it
in RIFE's class path but I could see no recompilation activity.
The second solution works if you run the project in Debug mode and
the Reload Changed Classes is available in the menu.
Not an optimal solution thought. :-)
Best regards,
Erik
On Jul 20, 2006, at 11:13 AM, Geert Bevin wrote:
Hi Erik,
the reason why it doesn't replace the class is because you're
probably mixing two modes of working.
You need to do one of these:
* you don't compile your elements yourself at all (nor IDEA) and
let RIFE do the work, then you can just save and reload
* you compile your elements yourself (or IDEA), but when you save
them you have to let IDEA compile it and this is usually done using
hotswap (with Eclipse this happens when you save, with IDEA you
have to select Reload changed classes from the Tools menu).
If you mix both, RIFE will not find the recompiled classes or not
recompile the sources itself.
Best regards,
Geert
On 20 Jul 2006, at 11:04, Erik Bogghed wrote:
Geert,
Using the 1.6M1-snapshot-jdk15 version RIFE no longer breaks, but
it doesn't replace the class either.
Reloading of modified templates still works.
Best regards,
Erik
On Jul 20, 2006, at 12:12 AM, Geert Bevin wrote:
Hi Erik,
thanks for reporting this. I investigated and it's indeed a bug
related to the Java site declaration and the dynamic reloading. I
fixed the bug and you can download the update snapshot in a few
hours from: http://rifers.org/downloads/rife/snapshots/
Please test if the fixed version solves the problem for you.
Best regards,
Geert
On 19 Jul 2006, at 20:10, Erik Bogghed wrote:
Hi,
I was testing dynamic reloading of classes in IDEA using the
09_stateful_counters example from rife-examples. I used
the Counter.java element. When I touched the class (saved it
without any changes) RIFE promptly recompiled it. When I
accessed the site it failed with
a"java.lang.IllegalArgumentException: object is not an instance
of declaring class".
I have located the problem to line 343 in
com.uwyn.rife.engine.OutputValues.java:
value = output_getter.getValue().invoke(mElement, (Object[])null);
When I looked at what happened during a successful run vs after
a recompile I couldn't see anything strange in the new
Counter instance (even though something is apparently). This is
a bit strange as dynamic reloading of templates works
fine. Is this a known problem regarding reflection and annotations?
Best regards,
Erik
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
