yes i know..
VAJ (which i used before eclipse and hotswap)
did it a bit better. It could handle changes of classes a bit more.
Í do get that when you add a instance var it can't handle that if there
are instances in mem
of that class..
What i don't get is why a method addition/removal is important/difficult
for hotswap.
It has nothing to really to do with a instance state.
johan
Joni Suominen wrote:
On Wed, 2005-08-24 at 08:36 +0200, Johan Compagner wrote:
so if i am reading this right, You also do the:
code, compile, deploy, debug/test, stop and then -> co...?
Why is everybody doing that? It is so immensely waste of time !!
Deploy only once or whenever the jvm really can't handly the hotswap of
a class
(when you add or remove a instance variable for example)
code/compile/debug/text is one step that you do at the same time
This is how i work since the beginning of my java years (around jdk
version 1.1.5)
Well, jvm hot swap suceeds only if you change the method body. So it
fails if you add method, add field, change signature etc. Hot swap
currently works only in very limited way. When it works, no redeployment
is needed.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
