news.eclipse.tools.ve

[news.eclipse.tools.ve] Re: Error Log filling up

richkulp@xxxxxxx (Rich Kulp) — Fri, 18 Sep 2009 13:40:20 GMT

If the VE is working otherwise, I guess it is ok.

cjob68@xxxxxxx 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

[news.eclipse.tools.ve] Re: Error Log filling up

cjob68@xxxxxxx (cjob68) — Fri, 18 Sep 2009 13:35:06 GMT

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 ?

[news.eclipse.tools.ve] Re: Error Log filling up

richkulp@xxxxxxx (Rich Kulp) — Thu, 17 Sep 2009 20:58:23 GMT

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

[news.eclipse.tools.ve] Re: Error Log filling up

richkulp@xxxxxxx (Rich Kulp) — Thu, 17 Sep 2009 20:50:53 GMT

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@xxxxxxx 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

[news.eclipse.tools.ve] Re: Error Log filling up

cjob68@xxxxxxx (cjob68) — Thu, 17 Sep 2009 19:28:41 GMT

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.

[news.eclipse.tools.ve] Re: Error Log filling up

cjob68@xxxxxxx (cjob68) — Thu, 17 Sep 2009 19:24:18 GMT

I think I may have found the issue. I removed GUI components one by one from the frame to see when I could add a space in the source and watch the GUI sync and generate an error. When I removed the jTextArea I no longer get the error when the GUI syncs. I'm not sure why this is happening but at least I am getting somewhere.

[news.eclipse.tools.ve] Re: Error Log filling up

cjob68@xxxxxxx (cjob68) — Thu, 17 Sep 2009 16:57:07 GMT

I'm also getting errors in another class that doesn't have any tables and for the most part it's got the same code that VE inserted.

The error is :

java.lang.NullPointerException
	at  org.eclipse.ve.internal.java.codegen.util.CodeGenUtil.create Instance(CodeGenUtil.java:103)
	at  org.eclipse.ve.internal.java.codegen.util.CodeGenUtil.create Instance(CodeGenUtil.java:116)
	at  org.eclipse.ve.internal.java.codegen.model.BeanPart.createEO bject(BeanPart.java:809)

Is this something I should be worried about ? Could my install of VE be corrupted ?

Any suggestions ?

[news.eclipse.tools.ve] Re: Error Log filling up

richkulp@xxxxxxx (Rich Kulp) — Thu, 17 Sep 2009 15:58:05 GMT

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@xxxxxxx 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 columnNamesV = new Vector(Arrays.asList(columnNames)); jTable = new JTable(getRowData(),columnNamesV);

My modified code which it doesn't like: String[] columnNames = {"Column1", "Column2"}; Vector columnNamesV = new Vector(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

[news.eclipse.tools.ve] Re: Error Log filling up

cjob68@xxxxxxx (cjob68) — Thu, 17 Sep 2009 15:44:37 GMT

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 columnNamesV = new Vector(Arrays.asList(columnNames));
jTable = new JTable(getRowData(),columnNamesV);


My modified code which it doesn't like:
String[] columnNames = {"Column1", "Column2"};
Vector columnNamesV = new Vector(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 ?

[news.eclipse.tools.ve] Re: Error Log filling up

richkulp@xxxxxxx (Rich Kulp) — Thu, 17 Sep 2009 13:17:56 GMT

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@xxxxxxx 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