| VE development problem [message #103974] |
Fri, 26 August 2005 19:01  |
Eclipse User |
|
|
|
Hi all,
I'm using VE 1.1.0.
Here are simple list of problems which I found:
1. At Runtime-Workbench I must close all editors and clean all projects to
REFRESH BEAN INFOs. Sometimes I have to change the JAVA file before I may
do the project cleaning. The beaninfo cache may be old, even if the
CLASSPATH CONTAINER JAR FILE CONTAINS NEW BEANINFO VERSION.
2. When I'm developing new palette with components the palette will not
show immediately when is CLASPATH CONTAINER INSERTED INTO THE TARGET
PROJECT!!!
The palette will show for next random period of TIME!!!! From that point
the palete is shown all the time.
3. The development is somethink hard when there are more VMs. This is only
the tip for development improvement.
John Cage
|
|
|
| Re: VE development problem [message #104113 is a reply to message #103974] |
Mon, 29 August 2005 09:26  |
| Eclipse User |
|
|
|
John Cage wrote:
> Hi all,
>
> I'm using VE 1.1.0.
> Here are simple list of problems which I found:
>
> 1. At Runtime-Workbench I must close all editors and clean all projects
> to REFRESH BEAN INFOs. Sometimes I have to change the JAVA file before I
> may do the project cleaning. The beaninfo cache may be old, even if the
> CLASSPATH CONTAINER JAR FILE CONTAINS NEW BEANINFO VERSION.
>
Changed BeanInfo is not a typical scenario; VE does not expect this to be changed
at this time... so you will have to "clean" to clear the cache.
> 2. When I'm developing new palette with components the palette will not
> show immediately when is CLASPATH CONTAINER INSERTED INTO THE TARGET
> PROJECT!!!
> The palette will show for next random period of TIME!!!! From that point
> the palete is shown all the time.
>
VE creates a "spare" VM when it opens an editor and keeps it around for 5min or so (in the case that no VE editors are
up). This VM will speed up the opening of an editor the next go around. ... the problem is that this VM will have the
classpath that was set on its creation time. If the class path was changed, VE should recycle All VMs (for open
editors, including the spare). .. if it does not it is a bug.
> 3. The development is somethink hard when there are more VMs. This is
> only the tip for development improvement.
>
Yes... debugging the target VM is a bit indirect (have to connect another debugger to the target); target VM has many
draw backs, but also many merits at the same time. Something we continuesly struggle with.
> John Cage
>
>
|
|
|
| Re: VE development problem [message #610426 is a reply to message #103974] |
Mon, 29 August 2005 09:26 |
| Eclipse User |
|
|
|
John Cage wrote:
> Hi all,
>
> I'm using VE 1.1.0.
> Here are simple list of problems which I found:
>
> 1. At Runtime-Workbench I must close all editors and clean all projects
> to REFRESH BEAN INFOs. Sometimes I have to change the JAVA file before I
> may do the project cleaning. The beaninfo cache may be old, even if the
> CLASSPATH CONTAINER JAR FILE CONTAINS NEW BEANINFO VERSION.
>
Changed BeanInfo is not a typical scenario; VE does not expect this to be changed
at this time... so you will have to "clean" to clear the cache.
> 2. When I'm developing new palette with components the palette will not
> show immediately when is CLASPATH CONTAINER INSERTED INTO THE TARGET
> PROJECT!!!
> The palette will show for next random period of TIME!!!! From that point
> the palete is shown all the time.
>
VE creates a "spare" VM when it opens an editor and keeps it around for 5min or so (in the case that no VE editors are
up). This VM will speed up the opening of an editor the next go around. ... the problem is that this VM will have the
classpath that was set on its creation time. If the class path was changed, VE should recycle All VMs (for open
editors, including the spare). .. if it does not it is a bug.
> 3. The development is somethink hard when there are more VMs. This is
> only the tip for development improvement.
>
Yes... debugging the target VM is a bit indirect (have to connect another debugger to the target); target VM has many
draw backs, but also many merits at the same time. Something we continuesly struggle with.
> John Cage
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04385 seconds
Home