Sorry, I meant the fix for the bug did not make 3.0 final but is in 3.0.1...
just tried it with in my war seam project. this is magic!.
does it support add new components (new classes) without restarting ?
I just tried that with the testInject Seam component from the tutorial and I got this exception:
Caused by: java.lang.Error: Unresolved compilation problem: testInject cannot be resolved
This may be due to the fact that JRebel detects changes to already deployed classes, not detecting and hot deploying new classes.
Is it possible with JRebel to add a new stateless session bean and inject it with the @EJB annotation into another SLSB, JSF based managed bean or servlet?
Adding new ejbs is not supported. Supporting injection into servlets shouldn't be to difficult, but adding a new ejb is probably difficult.
I don't have the definitive answer about adding new JavaBeans and/or Seam JavaBean components. You'll have to ask ZT support team.
Some related info: http://wikis.sun.com/display/mlvm/HotSwap
btw, everything JRebel, JVM HotSwap, and hot deploy are capable of (i.e. features comparison) is listed here: http://www.zeroturnaround.com/jrebel/comparison
Note that the
leaks memorymay not be 100% accurate due to the permgen space size growing on hot redeploys (I haven't checked this myself but you can check this yourself using the jconsole tool that ships with the Sun HotSpot JVM, this is not an issue with Oracle JRockit, it does not have a permgen space).
25%-30% less memory use. It is not uncommon to need a lot of PermGen heap with JRebel enabled, so we optimized memory use and will continue to drive it down in the upcoming milestones.
In your VM args, this is specified as follows: -XX:MaxPermSize=256m, so feel free to bump it up to 512m, etc. as required.
that is a small limitation for me, the speed of turnover is pretty good. thanks for the reply !