Hi,
i posted the Groovy-Support-Bug (issue 1655) because im really interested in reloading my managed beans dynamic on runtime (mostly for development).
but after reading a bit about classreloading on the web, i wonder if this is really necessary to use groovy for that.
So my basic idea is:
When a managed beans gets injected, and it does not exists in the scope yet, it should be possible to reload this class safely.
Simple because it does not exists before, you don't have to think about merging existing objects to the new class-version.
the result would be:
- requests scope can reload on every request
- session scope (and under scopes) can reload when session is created
- app scope -> restart the app
what sounds pretty good to me.
i would really appreciate your comments on this idea!
greetings Moritz
[Message sent by forum member 'moritzthielcke2']
http://forums.java.net/jive/thread.jspa?messageID=477290