#4 Application Refresh

[Max CHEVALIER]

There are 2 refreshment issues :
When modifying a bean and reload it in the application it
is srill the last version that is executed.

When removing and replacing a relation between two
components the last ont is still active when generate
the bean that can cause compilation errors.

MC.

[Masahiro Takatsuka]

Logged In: YES
user_id=145190

Thanks for the report,

I am aware of the first problem, and it's due to how a class
loader work in JVM. Basically, you cannot un-load the class
file which is loaded in the JVM. Technically, there are few
things we can do:

1) Use Java Debug Interface, which allow you to unload a
class. However, this function is only available on a
certain JVM. Therefore, supporting this would break the
platform independency.

2) Or, I have have a separate classloader for each bean
loaded. However, this would put a significant overhead and
class file management issue.

In the past, I've discussed this with Sun's JavaBean people,
but we could not find a good solution.

For the second behavior, I'll try to fix it ASAP.

In regards to JBeanStudio's source code, I now maintain the
sourcecode using Subversion, which is not supported by
SourceForge.

Thanks,
Masa