Home » Archived » Visual Editor (VE) » Eclipse 3.2, VE 1.2 NPE Parse Error
| Eclipse 3.2, VE 1.2 NPE Parse Error [message #127540] |
Tue, 04 July 2006 16:59  |
Eclipse User |
|
|
|
Originally posted by: chas.douglass.NOSPAMgmail.com
I have a frame that works fine under Eclipse 3.1.2 and VE 1.1(? whatever
the current update was).
Upgrading to 3.2 final and the update of VE (1.2.0v20060518_RC1) I get:
(java.lang.NullPointerException
at org.eclipse.ve.internal.java.codegen.model.BeanPart.getSimpl eName
(BeanPart.java:273)
at org.eclipse.ve.internal.java.codegen.model.BeanPart.getImpli citName
(BeanPart.java:282)
at org.eclipse.ve.internal.java.codegen.model.BeanPart.getSimpl eName
(BeanPart.java:276)
at
org.eclipse.ve.internal.java.codegen.model.BeanDeclModel.get UnreferencedB
eanParts(BeanDeclModel.java:791)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildCompo
sitionModel(JavaSourceTranslator.java:765)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reversePar
se(JavaSourceTranslator.java:874)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocu
ment(JavaSourceTranslator.java:947)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel
(JavaSourceTranslator.java:597)
at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart
$Setup.run(JavaVisualEditorPart.java:1978)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
With a "parse error" and no visual to edit.
This is a large frame with several split-panels and a bunch of tabbed
panels with tables with custom table-models.
Any ideas?
Chas Douglass
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #127647 is a reply to message #127540] |
Wed, 05 July 2006 14:21  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Is this the entire .log file?
You don't have the release version of VE installed. You should use
Callisto and step up to the released version VE instead of the RC1.
But, try clearing the cache first.
1) Open the VE, then close it and all other VE's.
2) Do Project->Clean...->Clean all... wait for build to finish.
3) Open the VE.
If that doesn't fix the problem, and stepping up to the released version
of VE doesn't fix it, could you please attach your class so we can take
a look?
--
Thanks,
Rich Kulp
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #127660 is a reply to message #127647] |
Wed, 05 July 2006 15:04 |
| Eclipse User |
|
|
|
Originally posted by: chas.douglass.NOSPAMgmail.com
Comments inline:
Rich Kulp <richkulp@us.NO_SPAM.ibm.com> wrote in
news:e8ghtu$pua$1@utils.eclipse.org:
> Is this the entire .log file?
No, but it's the only relevant part, I think. Just in case, here's a
full dump:
!SESSION 2006-07-05 07:33:07.476
-----------------------------------------------
eclipse.buildId=M20060629-1905 java.version=1.5.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.jem.beaninfo 2 0 2006-07-05 07:34:12.288
!MESSAGE
+++ Warning +++: Wed Jul 05 07:34:12 PDT 2006 Build job waiting when
trying to start beaninfo registry. Possible race.
!ENTRY org.eclipse.osgi 4 0 2006-07-05 07:34:15.976
!MESSAGE While loading class
" org.tigris.subversion.subclipse.ui.console.ConsoleDocument$C onsoleLine ",
thread "main" timed out waiting (5000ms) for thread "Worker-2" to finish
starting bundle "org.tigris.subversion.subclipse.ui". To avoid deadlock,
thread "main" is proceeding but
" org.tigris.subversion.subclipse.ui.console.ConsoleDocument$C onsoleLine "
may not be fully initialized. !STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .preFindLocal
Class(EclipseLazyStarter.java:75) at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(Class
pathManager.java:409) at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(D
efaultClassLoader.java:188) at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(Bund
leLoader.java:339) at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoa
der.java:391) at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoa
der.java:352) at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(Defaul
tClassLoader.java:83) at
java.lang.ClassLoader.loadClass(ClassLoader.java:251) at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319 ) at
org.tigris.subversion.subclipse.ui.console.ConsoleDocument.g etLines(Conso
leDocument.java:79) at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole. dump(SVNOutpu
tConsole.java:202) at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole. access$1(SVNO
utputConsole.java:199) at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$ 1.run(SVNOutp
utConsole.java:124) at
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5) at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:1
23) at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325) at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971) at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1914) at
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:41
9) at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149) at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:95)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivat
or.java:78) at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati
on(EclipseAppLauncher.java:92) at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(Eclips
eAppLauncher.java:68) at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:4
00) at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:1
77) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java
:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorI
mpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
!ENTRY org.eclipse.ve.java.core 2 0 2006-07-05 07:34:46.491
!MESSAGE Exception thrown.
!STACK 0
java.lang.NullPointerException
at
org.eclipse.ve.internal.java.codegen.model.BeanPart.getSimpl eName(BeanPar
t.java:273) at
org.eclipse.ve.internal.java.codegen.model.BeanPart.getImpli citName(BeanP
art.java:282) at
org.eclipse.ve.internal.java.codegen.model.BeanPart.getSimpl eName(BeanPar
t.java:276) at
org.eclipse.ve.internal.java.codegen.model.BeanDeclModel.get UnreferencedB
eanParts(BeanDeclModel.java:791) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildCompo
sitionModel(JavaSourceTranslator.java:765) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reversePar
se(JavaSourceTranslator.java:874) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocu
ment(JavaSourceTranslator.java:947) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(
JavaSourceTranslator.java:597) at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setu
p.run(JavaVisualEditorPart.java:1978) at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
> You don't have the release version of VE installed. You should use
> Callisto and step up to the released version VE instead of the RC1.
>
I'm now using eclipse Build id: M20060629-1905
VE 1.2.0.v20060530_RC2--IKUAYAAM (is that the correct release version?)
> But, try clearing the cache first.
>
> 1) Open the VE, then close it and all other VE's.
> 2) Do Project->Clean...->Clean all... wait for build to finish.
> 3) Open the VE.
>
No difference.
> If that doesn't fix the problem, and stepping up to the released
> version of VE doesn't fix it, could you please attach your class so we
> can take a look?
>
The class is 1800 lines of code, and part of a 20k LoC program so it
might be easier if you can provide me any way to trace where the error
is actually occurring.
I have tried removing various pieces, including changing the
initialize() method to bare bones, but so far I haven't been able to
change the error.
Thanks for your attention.
Chas Douglass
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #127673 is a reply to message #127660] |
Wed, 05 July 2006 15:20 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Yeah, that is the final release version of VE.
I don't know how to narrow it down. These kind of errors usually happen
due to some unexpected code pattern. But it is impossible to say what
that code pattern could be because we try to deduce as much as we can
from the code, but it isn't an hard and set pattern. It is more of a
heuristic.
Does it only occur on this one class or on different classes?
If you really don't mind (i.e nothing confidential) you could send the
class directly to me, not the newsgroup, and I can then turn on debug
and can trace exactly what happens and see if we can reproduce it. I
usually don't need the entire application for something like this. Just
the class, I can mock up most needed classes just so that I don't get
compilation errors. These kind of errors are usually syntactic so they
can be found without having everything completely accurate.
----
Thanks,
Rich Kulp
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #127864 is a reply to message #127673] |
Thu, 06 July 2006 23:02 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Thanks, I got your class and I found the problem.
There is an unusual coding pattern that we couldn't handle. It had to do
with thisFrame object:
JECFrame extends JFrame {
private JECFrame thisFrame = null;
JECFrame() {
thisFrame = this;
...
}
somemethod() {
thisFrame.getRootPanel()....
}
}
This was causing a lot of problems. I got rid of thisFrame and just used
this in its place and everything worked fine. There were some
information warning about accessing a method without a receiver, but
those are OK. They just mean that we can't actually call those methods
because they are not normal bean getter methods and we don't know how to
parse them.
I've sent the fixed up class back to you.
--
Thanks,
Rich Kulp
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #127903 is a reply to message #127864] |
Fri, 07 July 2006 03:17 |
| Eclipse User |
|
|
|
Originally posted by: chas.douglass.NOSPAMgmail.com
Thanks, Rich, that solves my problem.
Of course, it never occurred to me that it was an unusual coding
pattern, but that's what makes designing idiot-proof software so
difficult -- idiots are so darned clever.
Chas Douglass
Rich Kulp <richkulp@us.NO_SPAM.ibm.com> wrote in
news:e8k4q2$98h$1@utils.eclipse.org:
> Thanks, I got your class and I found the problem.
>
> There is an unusual coding pattern that we couldn't handle. It had to
> do
> with thisFrame object:
>
> JECFrame extends JFrame {
> private JECFrame thisFrame = null;
>
> JECFrame() {
> thisFrame = this;
> ...
> }
>
> somemethod() {
> thisFrame.getRootPanel()....
> }
> }
>
> This was causing a lot of problems. I got rid of thisFrame and just
> used
> this in its place and everything worked fine. There were some
> information warning about accessing a method without a receiver, but
> those are OK. They just mean that we can't actually call those methods
> because they are not normal bean getter methods and we don't know how
> to parse them.
>
> I've sent the fixed up class back to you.
>
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #613454 is a reply to message #127540] |
Wed, 05 July 2006 14:21 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Is this the entire .log file?
You don't have the release version of VE installed. You should use
Callisto and step up to the released version VE instead of the RC1.
But, try clearing the cache first.
1) Open the VE, then close it and all other VE's.
2) Do Project->Clean...->Clean all... wait for build to finish.
3) Open the VE.
If that doesn't fix the problem, and stepping up to the released version
of VE doesn't fix it, could you please attach your class so we can take
a look?
--
Thanks,
Rich Kulp
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #613455 is a reply to message #127647] |
Wed, 05 July 2006 15:04 |
 Chas Douglass
Messages: 26
Registered: July 2009 |
Junior Member |
|
|
Comments inline:
Rich Kulp <richkulp@us.NO_SPAM.ibm.com> wrote in
news:e8ghtu$pua$1@utils.eclipse.org:
> Is this the entire .log file?
No, but it's the only relevant part, I think. Just in case, here's a
full dump:
!SESSION 2006-07-05 07:33:07.476
-----------------------------------------------
eclipse.buildId=M20060629-1905 java.version=1.5.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.jem.beaninfo 2 0 2006-07-05 07:34:12.288
!MESSAGE
+++ Warning +++: Wed Jul 05 07:34:12 PDT 2006 Build job waiting when
trying to start beaninfo registry. Possible race.
!ENTRY org.eclipse.osgi 4 0 2006-07-05 07:34:15.976
!MESSAGE While loading class
" org.tigris.subversion.subclipse.ui.console.ConsoleDocument$C onsoleLine ",
thread "main" timed out waiting (5000ms) for thread "Worker-2" to finish
starting bundle "org.tigris.subversion.subclipse.ui". To avoid deadlock,
thread "main" is proceeding but
" org.tigris.subversion.subclipse.ui.console.ConsoleDocument$C onsoleLine "
may not be fully initialized. !STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .preFindLocal
Class(EclipseLazyStarter.java:75) at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(Class
pathManager.java:409) at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(D
efaultClassLoader.java:188) at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(Bund
leLoader.java:339) at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoa
der.java:391) at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoa
der.java:352) at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(Defaul
tClassLoader.java:83) at
java.lang.ClassLoader.loadClass(ClassLoader.java:251) at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319 ) at
org.tigris.subversion.subclipse.ui.console.ConsoleDocument.g etLines(Conso
leDocument.java:79) at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole. dump(SVNOutpu
tConsole.java:202) at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole. access$1(SVNO
utputConsole.java:199) at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$ 1.run(SVNOutp
utConsole.java:124) at
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5) at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:1
23) at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325) at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971) at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1914) at
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:41
9) at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149) at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:95)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivat
or.java:78) at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati
on(EclipseAppLauncher.java:92) at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(Eclips
eAppLauncher.java:68) at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:4
00) at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:1
77) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java
:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorI
mpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
!ENTRY org.eclipse.ve.java.core 2 0 2006-07-05 07:34:46.491
!MESSAGE Exception thrown.
!STACK 0
java.lang.NullPointerException
at
org.eclipse.ve.internal.java.codegen.model.BeanPart.getSimpl eName(BeanPar
t.java:273) at
org.eclipse.ve.internal.java.codegen.model.BeanPart.getImpli citName(BeanP
art.java:282) at
org.eclipse.ve.internal.java.codegen.model.BeanPart.getSimpl eName(BeanPar
t.java:276) at
org.eclipse.ve.internal.java.codegen.model.BeanDeclModel.get UnreferencedB
eanParts(BeanDeclModel.java:791) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildCompo
sitionModel(JavaSourceTranslator.java:765) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reversePar
se(JavaSourceTranslator.java:874) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocu
ment(JavaSourceTranslator.java:947) at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(
JavaSourceTranslator.java:597) at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setu
p.run(JavaVisualEditorPart.java:1978) at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
> You don't have the release version of VE installed. You should use
> Callisto and step up to the released version VE instead of the RC1.
>
I'm now using eclipse Build id: M20060629-1905
VE 1.2.0.v20060530_RC2--IKUAYAAM (is that the correct release version?)
> But, try clearing the cache first.
>
> 1) Open the VE, then close it and all other VE's.
> 2) Do Project->Clean...->Clean all... wait for build to finish.
> 3) Open the VE.
>
No difference.
> If that doesn't fix the problem, and stepping up to the released
> version of VE doesn't fix it, could you please attach your class so we
> can take a look?
>
The class is 1800 lines of code, and part of a 20k LoC program so it
might be easier if you can provide me any way to trace where the error
is actually occurring.
I have tried removing various pieces, including changing the
initialize() method to bare bones, but so far I haven't been able to
change the error.
Thanks for your attention.
Chas Douglass
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #613456 is a reply to message #127660] |
Wed, 05 July 2006 15:20 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Yeah, that is the final release version of VE.
I don't know how to narrow it down. These kind of errors usually happen
due to some unexpected code pattern. But it is impossible to say what
that code pattern could be because we try to deduce as much as we can
from the code, but it isn't an hard and set pattern. It is more of a
heuristic.
Does it only occur on this one class or on different classes?
If you really don't mind (i.e nothing confidential) you could send the
class directly to me, not the newsgroup, and I can then turn on debug
and can trace exactly what happens and see if we can reproduce it. I
usually don't need the entire application for something like this. Just
the class, I can mock up most needed classes just so that I don't get
compilation errors. These kind of errors are usually syntactic so they
can be found without having everything completely accurate.
----
Thanks,
Rich Kulp
|
|
|
| Re: Eclipse 3.2, VE 1.2 NPE Parse Error [message #613471 is a reply to message #127673] |
Thu, 06 July 2006 23:02 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Thanks, I got your class and I found the problem.
There is an unusual coding pattern that we couldn't handle. It had to do
with thisFrame object:
JECFrame extends JFrame {
private JECFrame thisFrame = null;
JECFrame() {
thisFrame = this;
...
}
somemethod() {
thisFrame.getRootPanel()....
}
}
This was causing a lot of problems. I got rid of thisFrame and just used
this in its place and everything worked fine. There were some
information warning about accessing a method without a receiver, but
those are OK. They just mean that we can't actually call those methods
because they are not normal bean getter methods and we don't know how to
parse them.
I've sent the fixed up class back to you.
--
Thanks,
Rich Kulp
|
|
| |
Goto Forum:
Current Time: Mon Sep 23 08:16:51 GMT 2024
Powered by FUDForum. Page generated in 0.03922 seconds |
] 
Search
Help
Register
Login
Home
