| Need help with a design view cache/reload problem [message #91855] |
Fri, 20 May 2005 16:07  |
Eclipse User |
|
|
|
Originally posted by: no.ddress.here
Eclipse 3.1.M7
VE N20050519 latest nightly
VE seems like it is failing to write or subsequently read some of the
cached property values. Cleaning the project after every time the
customizer is a workaround.
No errors appear in the log file.
Procedurally:
Open file containing my bean, invoke customizer on the bean, click OK to
implement code changes. (The correct values are present in the property
sheet; the expected code is generated and present in the java file.)
Save file.
Close file.
Open file.
(In the property sheet for my bean, at least one 'customized' string
property value is blank. However, the correct code statement is present
in the file. The design view shows the bean panel outline, but not the
contents of my bean. This appearance is consistent with the property
being blank.)
Close file.
Clean project.
Open file.
(Property sheet contents and design view are now fully correct.)
My log shows that the correct named property changes are being generated
for all values changed by the customizer.
If I customize just one value, then that will be the one property that
VE fails to reload.
|
|
|
|
|
|
|
|
| Re: Need help with a design view cache/reload problem [message #607814 is a reply to message #91855] |
Fri, 20 May 2005 18:15  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Are there any .log messages?
Gerald Rosenberg wrote:
> Eclipse 3.1.M7
> VE N20050519 latest nightly
>
> VE seems like it is failing to write or subsequently read some of the
> cached property values. Cleaning the project after every time the
> customizer is a workaround.
>
> No errors appear in the log file.
>
> Procedurally:
> Open file containing my bean, invoke customizer on the bean, click OK to
> implement code changes. (The correct values are present in the property
> sheet; the expected code is generated and present in the java file.)
>
> Save file.
> Close file.
> Open file.
> (In the property sheet for my bean, at least one 'customized' string
> property value is blank. However, the correct code statement is present
> in the file. The design view shows the bean panel outline, but not the
> contents of my bean. This appearance is consistent with the property
> being blank.)
>
> Close file.
> Clean project.
> Open file.
> (Property sheet contents and design view are now fully correct.)
>
> My log shows that the correct named property changes are being generated
> for all values changed by the customizer.
>
> If I customize just one value, then that will be the one property that
> VE fails to reload.
--
Thanks,
Rich Kulp
|
|
|
| Re: Need help with a design view cache/reload problem [message #607815 is a reply to message #91875] |
Fri, 20 May 2005 21:44 |
| Eclipse User |
|
|
|
In article <d6lnjv$r78$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
says...
> Are there any .log messages?
>
> Gerald Rosenberg wrote:
> > Eclipse 3.1.M7
> > VE N20050519 latest nightly
> >
> > VE seems like it is failing to write or subsequently read some of the
> > cached property values. Cleaning the project after every time the
> > customizer is a workaround.
> >
> > No errors appear in the log file.
> >
Unfortunately, no messages of any kind. I am still fairly new to VE's
code organization If you can give some guidence as to where in the code
VE is writing and reading the cache, I should be able to determine
whether the property is being persisted and with what value.
|
|
|
|
| Re: Need help with a design view cache/reload problem [message #607819 is a reply to message #91933] |
Sat, 21 May 2005 17:15 |
| Eclipse User |
|
|
|
In article <d6o06h$krl$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
says...
> Look in the .metadata directory of your workspace. The .log file is in
> there. That is where we put our log messages.
>
>
Of course. I have spent all too much time looking at the sometimes
prodigious output of VE in that file.
Now, if I clear that log, start Eclipse and run through the procedure
previously outlined, then look at the log file (help->about->
configuration details->view error log, so I am sure to be looking at the
correct log) it contains no messages, error or otherwise. I am getting
a clean run as far as Eclipse and VE are concerned.
|
|
|
|
Powered by
FUDForum. Page generated in 0.09310 seconds
Home