Geert Bevin wrote:
This is just an organizational thing. RIFE doesn't care which
directories you put things in.
Thanks!
Next question(s), if I may: Is there any documentation explaining
exactly what the rules are for whether a class will be
reloaded/recompiled on the fly by RIFE's engine classloader, and for
that matter a description of all the stuff the classloader does? Is the
reloading just for element implementation classes? Those seem to
recompile reliably for me, but helper classes, data objects and the like
usually require hotswap and/or server restarts.
Why does the Jumpstart archive put "lib" in the -Drife.webapp.path
variable? Is that just for doing metadata merging on classes in library
jarfiles?
Maybe a more concrete example.
1. Unpack the Jumpstart zipfile
2. Run "ant run" from a shell prompt
3. Load the start page up in a browser
4. Make a change to
src/java/com/uwyn/rife/jumpstart/ApplicationVersion.java so it, say,
prints a line to System.out in its getVersion() or getVersionString()
methods
5. Make a similar change to
src/implementations/com/uwyn/rife/jumpstart/elements/Version.java
6. Reload the start page
When I do that, the change I made to ApplicationVersion.java does not
take effect, but the change to Version.java does. I have not found any
documentation on exactly what the RIFE classloader is *supposed* to be
doing in various contexts, so I am not sure if this is normal expected
behavior or a sign that something is screwy about my setup. Hopefully
it's all documented somewhere I haven't seen yet -- if so I will of
course stick something on the Wiki to help out the next person who has
the same questions.
-Steve
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
