Ah, this sounds like an extremely useful capability...
Java has a hot-swap capability... This is used, for example,
by Eclipse when you modify and recompile a piece of code while
the debugger is running. So to some extent, you get this for
free if you use Eclipse as the development environment.
Chad,
I think that you need to consider the classloader issues in order to be
able to do this. The JVM loads a class using the default ClassLoader --
which I think caches the class so that it needn't load it again.
So...even if you get it reinserted into the Ptolemy hierarchy, the JVM
will
I think it makes more sense to use Java's classloader to do this (as Matt
suggests) rather than hot-swap.
With hot-swap, the classes are expected to be consistent with one another
(as with a debugger, for instance)
Since there is no way to ensure this, an exception will likely result.
We've
Shouldn't removing the actor also be done in a ChangeRequest?
This seems like a very puzzling thing to do... What are you trying
to accomplish?
Edward
At 10:34 AM 11/21/2003 -0800, Chad Berkley wrote:
hi,
I'm trying to remove and actor from the actorLibrary model, change it,
then re-add it.
hi,
I'm trying to remove and actor from the actorLibrary model, change it,
then re-add it. For some reason, when it re-adds, you don't see the
changes that were made.
Here's the code that I'm using:
List l = actorLibrary.entityList();
for(int i=0; il.size(); i++)
{ //look for the actor in
