I just released version 0.2, which should contain some bug fixes for the seam integration.
It might be helpful to explain what's different with this approach compared to hotswap so users know when to use each.
The approach recompiles your classes on the fly as they are loaded into the JVM to allow them to be replaced later.
- Compared to hotswap
Hotswap only allows you to replace method bodies. Fakreplace can allow you to replace much more, including methods, fields and annotations. It does not however allow you to change superclasses or interfaces.
- Compared to app server hot deploy
It is much faster than an application server hot deploy, as it only replaces the modified classes and does not totally re-initialise the application. However an app server hot deploy allows you to change everything about your class including superclasses / interfaces.
This is still all fairly experimental, and is probably a similar approach to how JRebel / Weblogic fast swap work, however I have not used either of these so I am not sure.