| Can't open visual editor Eclipse 3.0 (with recommended versions) [message #47117] |
Mon, 05 July 2004 12:08  |
Eclipse User |
|
|
|
I get the following exception when trying to open one of my Java classes
with the visual editor.
java.lang.NullPointerException
at
org.eclipse.ve.internal.java.codegen.java.ExpressionDecoderF actory.getExpDec
oder(ExpressionDecoderFactory.java:98)
at
org.eclipse.ve.internal.java.codegen.model.BeanPart.setEObje ct(BeanPart.java
:478)
at
org.eclipse.ve.internal.java.codegen.model.BeanPart.createEO bject(BeanPart.j
ava:842)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.createJavaIns
tances(JavaSourceTranslator.java:690)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
ionModel(JavaSourceTranslator.java:771)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
t(JavaSourceTranslator.java:878)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
aSourceTranslator.java:653)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
un(JavaVisualEditorPart.java:1410)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
This is with Eclipse 3.0, VEs20040628, GEF 3.0 and EMF 2.0 (the recommended
for Eclipse 3.0).
The class in question is a subclass of JPanel containing our proprietory
java beans, which have
various complex customizable properties. However, the editor does open in
Eclipse 2.1.2 with VE 0.5.0,
even though it cannot properly parse all of the complex expressions that
are the values of the java beans properties.
Any ideas anyone?
|
|
|
|
|
| Re: Can't open visual editor Eclipse 3.0 (with recommended versions) [message #47834 is a reply to message #47746] |
Tue, 06 July 2004 11:07  |
| Eclipse User |
|
|
|
I tried deleting the .project and .classpath files within this project,
reset the
dependent projects etc. to exactly the same values as before, then rebuilt
the project. The visual editor now works with this rogue project, even
though
the .project and .classpath, and all project properties are the same as
before.
I even compared with the original version of the project from the cvs head,
and
could find no differences.
The important thing for me is that it now works, but the
reason remains a mystery...
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:ccecve$dgm$3@eclipse.org...
> It could be. Could you please open a bugzilla and attach your project
> zipped up to the bug report? Give us the version that fails. And tell us
> what the two classes in question are. It would be great if you could
> simplify it down to just the two classes and it still fails for you.
>
> That way we can see if there is something about the class that is
> causing the problem.
>
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
| Re: Can't open visual editor Eclipse 3.0 (with recommended versions) [message #594229 is a reply to message #47117] |
Mon, 05 July 2004 12:40 |
| Eclipse User |
|
|
|
In fact, this only seems to occur when my panel is in the same project as
the visual java beans in question! When I move the panel to another project
and make the new project dependent upon the one containing the visual java
beans,
the editor opens up ok. Is this a bug?
Darren Hurt
"Darren Hurt" <darren.hurt@coexis.com> wrote in message
news:ccbu9k$ec3$1@eclipse.org...
> I get the following exception when trying to open one of my Java classes
> with the visual editor.
>
> java.lang.NullPointerException
> at
>
org.eclipse.ve.internal.java.codegen.java.ExpressionDecoderF actory.getExpDec
> oder(ExpressionDecoderFactory.java:98)
> at
>
org.eclipse.ve.internal.java.codegen.model.BeanPart.setEObje ct(BeanPart.java
> :478)
> at
>
org.eclipse.ve.internal.java.codegen.model.BeanPart.createEO bject(BeanPart.j
> ava:842)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.createJavaIns
> tances(JavaSourceTranslator.java:690)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
> ionModel(JavaSourceTranslator.java:771)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
> t(JavaSourceTranslator.java:878)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
> aSourceTranslator.java:653)
> at
>
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> un(JavaVisualEditorPart.java:1410)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> This is with Eclipse 3.0, VEs20040628, GEF 3.0 and EMF 2.0 (the
recommended
> for Eclipse 3.0).
>
>
> The class in question is a subclass of JPanel containing our proprietory
> java beans, which have
> various complex customizable properties. However, the editor does open in
> Eclipse 2.1.2 with VE 0.5.0,
> even though it cannot properly parse all of the complex expressions that
> are the values of the java beans properties.
>
> Any ideas anyone?
>
>
>
>
>
|
|
|
| Re: Can't open visual editor Eclipse 3.0 (with recommended versions) [message #594451 is a reply to message #47146] |
Tue, 06 July 2004 10:29 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
It could be. Could you please open a bugzilla and attach your project
zipped up to the bug report? Give us the version that fails. And tell us
what the two classes in question are. It would be great if you could
simplify it down to just the two classes and it still fails for you.
That way we can see if there is something about the class that is
causing the problem.
--
Thanks, Rich Kulp
|
|
|
| Re: Can't open visual editor Eclipse 3.0 (with recommended versions) [message #594472 is a reply to message #47746] |
Tue, 06 July 2004 11:07 |
| Eclipse User |
|
|
|
I tried deleting the .project and .classpath files within this project,
reset the
dependent projects etc. to exactly the same values as before, then rebuilt
the project. The visual editor now works with this rogue project, even
though
the .project and .classpath, and all project properties are the same as
before.
I even compared with the original version of the project from the cvs head,
and
could find no differences.
The important thing for me is that it now works, but the
reason remains a mystery...
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:ccecve$dgm$3@eclipse.org...
> It could be. Could you please open a bugzilla and attach your project
> zipped up to the bug report? Give us the version that fails. And tell us
> what the two classes in question are. It would be great if you could
> simplify it down to just the two classes and it still fails for you.
>
> That way we can see if there is something about the class that is
> causing the problem.
>
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07670 seconds
Home