|
Re: Error Log filling up [message #486245 is a reply to message #486215] |
Wed, 16 September 2009 21:15 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Hi,
Sometimes there is a stalecache problem. This may be a symptom of that.
The way to get the cache cleared is to:
1) Open a VE
2) Close the VE
3) Project->Clean->Clean all
4) Wait for build to finish
5) Open a VE.
Hopefully you won't get any more such errors.
> Thanks in advance
>
>
--
Thanks,
Rich Kulp
|
|
|
|
Re: Error Log filling up [message #486371 is a reply to message #486247] |
Thu, 17 September 2009 13:17 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Hi,
Not -clean. That clears only the plugin configurations. It doesn't clear
cached metadata. You need to use the procedure I outlined to clear the
cached metadata.
Actually -clean should rarely be needed except if you are just putting
plugins directly into the eclipse configuration without using the
install manager or the dropins folder.
cjob68@shaw.ca wrote:
> I thought that might be the issue because Eclipse opened with an error
> today so I did run a -clean on it when I opened it again but that didn't
> fix this error. I'm not sure what the issue could be.
--
Thanks,
Rich Kulp
|
|
|
|
Re: Error Log filling up [message #486441 is a reply to message #486432] |
Thu, 17 September 2009 15:58 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Yeah, I could see that being a problem. The VE needs to be able to
instantiate a visual component. A non-static inner class can't be
instantiated.
cjob68@shaw.ca wrote:
> Thanks , I tried that but it didn't seem to fix it. I think I may know
> what the problem is. I have modified the section where the visual editor
> creates the jTable and the visual editor doesn't like this.
> Visual Editor likes this:
> String[] columnNames = {"Column1", "Column2"};
> Vector<String> columnNamesV = new
> Vector<String>(Arrays.asList(columnNames));
> jTable = new JTable(getRowData(),columnNamesV);
>
>
> My modified code which it doesn't like:
> String[] columnNames = {"Column1", "Column2"};
> Vector<String> columnNamesV = new
> Vector<String>(Arrays.asList(columnNames));
> jTable = new JTable(getRowData(),columnNamesV){
> ...custom table code here including creating a rendered to modify the
> color of the rows
> };
>
> Any ideas ?
--
Thanks,
Rich Kulp
|
|
|
|
|
|
Re: Error Log filling up [message #486495 is a reply to message #486482] |
Thu, 17 September 2009 20:50 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I'm not sure why either but there is a workaround you can use to have VE
ignore the line. It's kind of kludgy. We never got to put in an
annotation that would tell VE to ignore something when I was working on
VE. :-(
if(false)
;
else
jTextArea.getDocument().addDocumentListener(new MyDocumentListener());
This will work because VE is designed to ignore the else block of an if
statement.
cjob68@shaw.ca wrote:
> I found the line that is causing the problem.
> jTextArea.getDocument().addDocumentListener(new MyDocumentListener());
>
> I'm not sure why VE doesn't like this line. The code compiles fine and
> it also runs fine but when syncing the GUI it generates an error in the
> Error Log.
--
Thanks,
Rich Kulp
|
|
|
Re: Error Log filling up [message #486498 is a reply to message #486495] |
Thu, 17 September 2009 20:58 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Rich Kulp wrote:
> We never got to put in an
> annotation that would tell VE to ignore something when I was working on
> VE. :-(
A little bit of grammar problem there. It is not that we never put in
code to have something ignored only when I was working on VE! And so by
corollary when I'm not working on the VE it wouldn't ignore something. :-)
--
Thanks,
Rich Kulp
|
|
|
|
Re: Error Log filling up [message #486641 is a reply to message #486633] |
Fri, 18 September 2009 13:40 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If the VE is working otherwise, I guess it is ok.
cjob68@shaw.ca wrote:
> Are there any issues with just leaving my code as is and let VE generate
> those errors ?
> My concern with adding the code as described is it will make the code
> harder to read and also what happens if in a future release the issue is
> fixed ?
--
Thanks,
Rich Kulp
|
|
|
|
Re: Error Log filling up [message #617425 is a reply to message #486247] |
Thu, 17 September 2009 13:17 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Hi,
Not -clean. That clears only the plugin configurations. It doesn't clear
cached metadata. You need to use the procedure I outlined to clear the
cached metadata.
Actually -clean should rarely be needed except if you are just putting
plugins directly into the eclipse configuration without using the
install manager or the dropins folder.
cjob68@shaw.ca wrote:
> I thought that might be the issue because Eclipse opened with an error
> today so I did run a -clean on it when I opened it again but that didn't
> fix this error. I'm not sure what the issue could be.
--
Thanks,
Rich Kulp
|
|
|
|
Re: Error Log filling up [message #617427 is a reply to message #486432] |
Thu, 17 September 2009 15:58 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Yeah, I could see that being a problem. The VE needs to be able to
instantiate a visual component. A non-static inner class can't be
instantiated.
cjob68@shaw.ca wrote:
> Thanks , I tried that but it didn't seem to fix it. I think I may know
> what the problem is. I have modified the section where the visual editor
> creates the jTable and the visual editor doesn't like this.
> Visual Editor likes this:
> String[] columnNames = {"Column1", "Column2"};
> Vector<String> columnNamesV = new
> Vector<String>(Arrays.asList(columnNames));
> jTable = new JTable(getRowData(),columnNamesV);
>
>
> My modified code which it doesn't like:
> String[] columnNames = {"Column1", "Column2"};
> Vector<String> columnNamesV = new
> Vector<String>(Arrays.asList(columnNames));
> jTable = new JTable(getRowData(),columnNamesV){
> ...custom table code here including creating a rendered to modify the
> color of the rows
> };
>
> Any ideas ?
--
Thanks,
Rich Kulp
|
|
|
|
|
Re: Error Log filling up [message #617431 is a reply to message #486482] |
Thu, 17 September 2009 20:50 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I'm not sure why either but there is a workaround you can use to have VE
ignore the line. It's kind of kludgy. We never got to put in an
annotation that would tell VE to ignore something when I was working on
VE. :-(
if(false)
;
else
jTextArea.getDocument().addDocumentListener(new MyDocumentListener());
This will work because VE is designed to ignore the else block of an if
statement.
cjob68@shaw.ca wrote:
> I found the line that is causing the problem.
> jTextArea.getDocument().addDocumentListener(new MyDocumentListener());
>
> I'm not sure why VE doesn't like this line. The code compiles fine and
> it also runs fine but when syncing the GUI it generates an error in the
> Error Log.
--
Thanks,
Rich Kulp
|
|
|
Re: Error Log filling up [message #617432 is a reply to message #486495] |
Thu, 17 September 2009 20:58 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Rich Kulp wrote:
> We never got to put in an
> annotation that would tell VE to ignore something when I was working on
> VE. :-(
A little bit of grammar problem there. It is not that we never put in
code to have something ignored only when I was working on VE! And so by
corollary when I'm not working on the VE it wouldn't ignore something. :-)
--
Thanks,
Rich Kulp
|
|
|
|
Re: Error Log filling up [message #617434 is a reply to message #617433] |
Fri, 18 September 2009 13:40 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If the VE is working otherwise, I guess it is ok.
cjob68@shaw.ca wrote:
> Are there any issues with just leaving my code as is and let VE generate
> those errors ?
> My concern with adding the code as described is it will make the code
> harder to read and also what happens if in a future release the issue is
> fixed ?
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.06027 seconds