Home » Archived » Visual Editor (VE) » Problem running VE 0.5.0
| Problem running VE 0.5.0 [message #19140] |
Mon, 16 February 2004 18:10  |
Eclipse User |
|
|
|
Originally posted by: tobias.kastl.freenet.de
Hello @everyone!
I tried the VE under Win2k and was enthusiastic. So I tried to install it
under Linux (Debian Kernel 2.6.1, eclipse 2.1.2, GEF-runtime-I20031015,
emf_1.1.1_20031020_1612WL.zip) too. The installation succeeded, but, when
I try to create a new VisualClass I get a NullPointerException and the
logfile shows the following Information:
!SESSION Feb 16, 2004 19:05:58.530
---------------------------------------------
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -install
file:/usr/share/eclipse/
!ENTRY org.eclipse.ve.java.core 4 0 Feb 16, 2004 19:05:58.532
!MESSAGE Exception
!STACK 0
java.lang.NullPointerException
at org.eclipse.core.runtime.CoreException.<init>(CoreException.java:35)
at
org.eclipse.jem.internal.proxy.core.ProxyPlugin.exec(ProxyPl ugin.java:414)
at
org.eclipse.jem.internal.proxy.core.ProxyVMRunner.exec(Proxy VMRunner.java:20)
at
org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRunner.java:230)
at
org.eclipse.jem.internal.proxy.remote.ProxyRegistration.star tImplementation(ProxyRegistration.java:206)
at
org.eclipse.jem.internal.proxy.core.ProxyPlugin.startImpleme ntation(ProxyPlugin.java:165)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart.createProxyFactoryRegistry(JavaVisualEditorPart.jav a:667)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.initializeForProject(JavaVisualEditorPart.jav a:1800)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.initialize(JavaVisualEditorPart.java:1705)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1588)
at java.lang.Thread.run(Thread.java:534)
I already did a chmod on the installation directory.
So, could you please help me and tell me, where I did wrong.
Thank you very much,
best wishes,
Tobi
|
|
|
| Re: Problem running VE 0.5.0 [message #19217 is a reply to message #19140] |
Mon, 16 February 2004 18:52  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Looking in the code the null pointer exception occurred because we had
trapped an IOException and was trying to turn it into a CoreException,
except we made mistake and had some bad code.
The basic problem is that we were trying to do a:
Runtime.getRuntime().exec(...)
and an IOException was thrown.
Unfortunately we lost what the actual I/O exception was that actually
happened.
Something about your setup prevented us from doing an exec() line.
Since this code is not that much different then the standard java
application launcher used by straight Eclipse, try this:
1) Create a class with a main
2) Use Launch As Java Application against this class.
See if the standard launcher will have an I/O exception too and print
off what the problem was.
--
Thanks, Rich Kulp
|
|
|
| Re: Problem running VE 0.5.0 [message #19228 is a reply to message #19217] |
Mon, 16 February 2004 21:36 |
| Eclipse User |
|
|
|
Originally posted by: tobias.kastl.freenet.de
Back again,
thank you very much for your answer,
I did as you suggested and got another Exception trying to run a normal
Application.
Here comes the stacktrace:
!SESSION Feb 16, 2004 22:34:30.948
---------------------------------------------
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -install
file:/usr/share/ecl
ipse/
!ENTRY org.eclipse.debug.ui 4 120 Feb 16, 2004 22:34:30.950
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[120]: java.io.IOException:
java.io.IOExce
ption: /usr/share/j2sdk1.4.2_03/bin/java: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
at
org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
:59)
at
org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
ner.java:230)
at
org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
iguration.java:156)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
gin.java:676)
at
org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
8)
at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
Context.java:101)
!ENTRY org.eclipse.debug.core 4 120 Feb 16, 2004 22:34:30.951
!MESSAGE Exception occurred executing command line.
!STACK 0
java.io.IOException: java.io.IOException:
/usr/share/j2sdk1.4.2_03/bin/java: can
not execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
at
org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
:59)
at
org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
ner.java:230)
at
org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
iguration.java:156)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
gin.java:676)
at
org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
8)
at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
Context.java:101)
I think we're on the right way but I'm afraid I still don't know where to
go. ;)
Be so kind and do another suggestion.
best wishes, Tobi
Rich Kulp wrote:
> Looking in the code the null pointer exception occurred because we had
> trapped an IOException and was trying to turn it into a CoreException,
> except we made mistake and had some bad code.
> The basic problem is that we were trying to do a:
> Runtime.getRuntime().exec(...)
> and an IOException was thrown.
> Unfortunately we lost what the actual I/O exception was that actually
> happened.
> Something about your setup prevented us from doing an exec() line.
> Since this code is not that much different then the standard java
> application launcher used by straight Eclipse, try this:
> 1) Create a class with a main
> 2) Use Launch As Java Application against this class.
> See if the standard launcher will have an I/O exception too and print
> off what the problem was.
|
|
|
| Re: Problem running VE 0.5.0 [message #19246 is a reply to message #19228] |
Mon, 16 February 2004 21:40 |
| Eclipse User |
|
|
|
Originally posted by: tobias.kastl.freenet.de
Ha! After reading what I posted I found out what was missing.
I changed the access-rights for the eclipse-installation, but not for my
j2sdk.
There was the problem. After chmodding the sdk-directory it worked.
Thank you very much for your help,
bye, bye,
Tobi
Tobi wrote:
> Back again,
> thank you very much for your answer,
> I did as you suggested and got another Exception trying to run a normal
> Application.
> Here comes the stacktrace:
> !SESSION Feb 16, 2004 22:34:30.948
> ---------------------------------------------
> java.version=1.4.2_03
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -os linux -ws gtk -arch x86 -install
> file:/usr/share/ecl
> ipse/
> !ENTRY org.eclipse.debug.ui 4 120 Feb 16, 2004 22:34:30.950
> !MESSAGE Error logged from Debug UI:
> !STACK 1
> org.eclipse.core.runtime.CoreException[120]: java.io.IOException:
> java.io.IOExce
> ption: /usr/share/j2sdk1.4.2_03/bin/java: cannot execute
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
> at java.lang.Runtime.execInternal(Native Method)
> at java.lang.Runtime.exec(Runtime.java:566)
> at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
> at
> org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
> :59)
> at
> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
> ner.java:230)
> at
> org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
>
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
> iguration.java:156)
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
> gin.java:676)
> at
> org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
> 8)
> at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
> Context.java:101)
> !ENTRY org.eclipse.debug.core 4 120 Feb 16, 2004 22:34:30.951
> !MESSAGE Exception occurred executing command line.
> !STACK 0
> java.io.IOException: java.io.IOException:
> /usr/share/j2sdk1.4.2_03/bin/java: can
> not execute
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
> at java.lang.Runtime.execInternal(Native Method)
> at java.lang.Runtime.exec(Runtime.java:566)
> at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
> at
> org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
> :59)
> at
> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
> ner.java:230)
> at
> org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
>
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
> iguration.java:156)
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
> gin.java:676)
> at
> org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
> 8)
> at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
> Context.java:101)
> I think we're on the right way but I'm afraid I still don't know where to
> go. ;)
> Be so kind and do another suggestion.
> best wishes, Tobi
> Rich Kulp wrote:
> > Looking in the code the null pointer exception occurred because we had
> > trapped an IOException and was trying to turn it into a CoreException,
> > except we made mistake and had some bad code.
> > The basic problem is that we were trying to do a:
> > Runtime.getRuntime().exec(...)
> > and an IOException was thrown.
> > Unfortunately we lost what the actual I/O exception was that actually
> > happened.
> > Something about your setup prevented us from doing an exec() line.
> > Since this code is not that much different then the standard java
> > application launcher used by straight Eclipse, try this:
> > 1) Create a class with a main
> > 2) Use Launch As Java Application against this class.
> > See if the standard launcher will have an I/O exception too and print
> > off what the problem was.
|
|
|
| Re: Problem running VE 0.5.0 [message #581297 is a reply to message #19140] |
Mon, 16 February 2004 18:52 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Looking in the code the null pointer exception occurred because we had
trapped an IOException and was trying to turn it into a CoreException,
except we made mistake and had some bad code.
The basic problem is that we were trying to do a:
Runtime.getRuntime().exec(...)
and an IOException was thrown.
Unfortunately we lost what the actual I/O exception was that actually
happened.
Something about your setup prevented us from doing an exec() line.
Since this code is not that much different then the standard java
application launcher used by straight Eclipse, try this:
1) Create a class with a main
2) Use Launch As Java Application against this class.
See if the standard launcher will have an I/O exception too and print
off what the problem was.
--
Thanks, Rich Kulp
|
|
|
| Re: Problem running VE 0.5.0 [message #581315 is a reply to message #19217] |
Mon, 16 February 2004 21:36 |
 Tobi 
Messages: 3
Registered: May 2010 |
Junior Member |
|
|
Back again,
thank you very much for your answer,
I did as you suggested and got another Exception trying to run a normal
Application.
Here comes the stacktrace:
!SESSION Feb 16, 2004 22:34:30.948
---------------------------------------------
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -install
file:/usr/share/ecl
ipse/
!ENTRY org.eclipse.debug.ui 4 120 Feb 16, 2004 22:34:30.950
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[120]: java.io.IOException:
java.io.IOExce
ption: /usr/share/j2sdk1.4.2_03/bin/java: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
at
org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
:59)
at
org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
ner.java:230)
at
org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
iguration.java:156)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
gin.java:676)
at
org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
8)
at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
Context.java:101)
!ENTRY org.eclipse.debug.core 4 120 Feb 16, 2004 22:34:30.951
!MESSAGE Exception occurred executing command line.
!STACK 0
java.io.IOException: java.io.IOException:
/usr/share/j2sdk1.4.2_03/bin/java: can
not execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
at
org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
:59)
at
org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
ner.java:230)
at
org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
iguration.java:156)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
gin.java:676)
at
org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
8)
at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
Context.java:101)
I think we're on the right way but I'm afraid I still don't know where to
go. ;)
Be so kind and do another suggestion.
best wishes, Tobi
Rich Kulp wrote:
> Looking in the code the null pointer exception occurred because we had
> trapped an IOException and was trying to turn it into a CoreException,
> except we made mistake and had some bad code.
> The basic problem is that we were trying to do a:
> Runtime.getRuntime().exec(...)
> and an IOException was thrown.
> Unfortunately we lost what the actual I/O exception was that actually
> happened.
> Something about your setup prevented us from doing an exec() line.
> Since this code is not that much different then the standard java
> application launcher used by straight Eclipse, try this:
> 1) Create a class with a main
> 2) Use Launch As Java Application against this class.
> See if the standard launcher will have an I/O exception too and print
> off what the problem was.
|
|
|
| Re: Problem running VE 0.5.0 [message #581337 is a reply to message #19228] |
Mon, 16 February 2004 21:40 |
Tobi
Messages: 3
Registered: May 2010 |
Junior Member |
|
|
Ha! After reading what I posted I found out what was missing.
I changed the access-rights for the eclipse-installation, but not for my
j2sdk.
There was the problem. After chmodding the sdk-directory it worked.
Thank you very much for your help,
bye, bye,
Tobi
Tobi wrote:
> Back again,
> thank you very much for your answer,
> I did as you suggested and got another Exception trying to run a normal
> Application.
> Here comes the stacktrace:
> !SESSION Feb 16, 2004 22:34:30.948
> ---------------------------------------------
> java.version=1.4.2_03
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -os linux -ws gtk -arch x86 -install
> file:/usr/share/ecl
> ipse/
> !ENTRY org.eclipse.debug.ui 4 120 Feb 16, 2004 22:34:30.950
> !MESSAGE Error logged from Debug UI:
> !STACK 1
> org.eclipse.core.runtime.CoreException[120]: java.io.IOException:
> java.io.IOExce
> ption: /usr/share/j2sdk1.4.2_03/bin/java: cannot execute
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
> at java.lang.Runtime.execInternal(Native Method)
> at java.lang.Runtime.exec(Runtime.java:566)
> at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
> at
> org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
> :59)
> at
> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
> ner.java:230)
> at
> org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
>
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
> iguration.java:156)
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
> gin.java:676)
> at
> org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
> 8)
> at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
> Context.java:101)
> !ENTRY org.eclipse.debug.core 4 120 Feb 16, 2004 22:34:30.951
> !MESSAGE Exception occurred executing command line.
> !STACK 0
> java.io.IOException: java.io.IOException:
> /usr/share/j2sdk1.4.2_03/bin/java: can
> not execute
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
> at java.lang.Runtime.execInternal(Native Method)
> at java.lang.Runtime.exec(Runtime.java:566)
> at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:471 )
> at
> org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java
> :59)
> at
> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRun
> ner.java:230)
> at
> org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunc hConfigur
>
ationDelegate.launch(JavaLocalApplicationLaunchConfiguration Delegate.java:111)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConf
> iguration.java:156)
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlu
> gin.java:676)
> at
> org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:53
> 8)
> at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:48 7)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(Modal
> Context.java:101)
> I think we're on the right way but I'm afraid I still don't know where to
> go. ;)
> Be so kind and do another suggestion.
> best wishes, Tobi
> Rich Kulp wrote:
> > Looking in the code the null pointer exception occurred because we had
> > trapped an IOException and was trying to turn it into a CoreException,
> > except we made mistake and had some bad code.
> > The basic problem is that we were trying to do a:
> > Runtime.getRuntime().exec(...)
> > and an IOException was thrown.
> > Unfortunately we lost what the actual I/O exception was that actually
> > happened.
> > Something about your setup prevented us from doing an exec() line.
> > Since this code is not that much different then the standard java
> > application launcher used by straight Eclipse, try this:
> > 1) Create a class with a main
> > 2) Use Launch As Java Application against this class.
> > See if the standard launcher will have an I/O exception too and print
> > off what the problem was.
|
|
|
Goto Forum:
Current Time: Sat Dec 21 16:57:54 GMT 2024
Powered by FUDForum. Page generated in 0.02978 seconds |
] 
Search
Help
Register
Login
Home
