Categories » BEAM Development » Launcher error
Combination View Flat View Tree View
Threads [ Previous | Next ]
Launcher error
toggle
Launcher error
11/17/09 3:21 PM
Hi,
I am still struggling to get the development environment to work as described here http://www.brockmann-consult.de/beam-wiki/display/BEAM/Build+from+Source. It proves to be very hard for a Maven/Ceres newbie and a nearly Eclipse/Java newbie....

I imported the ceres and beam projects in Eclipse 3.2 (using java-6-sun-1.6.0.16). Now I am trying to run the beam-visat project with the Run configuration as described in step 12 but I am getting this error:


DEBUG] ceres-launcher: Configuration type: com.bc.ceres.core.runtime.internal.DefaultRuntimeConfig
[DEBUG] ceres-launcher: Classpath type: com.bc.ceres.launcher.internal.BootstrapClasspathFactory
[DEBUG] ceres-launcher: 0 library(s) added to classpath
Error: null
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bc.ceres.launcher.Launcher.launch(Launcher.java:99)
at com.bc.ceres.launcher.Launcher.main(Launcher.java:33)
Caused by: java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:182)
at java.util.StringTokenizer.<init>(StringTokenizer.java:204)
at com.bc.ceres.core.runtime.internal.SplashScreenProgressMonitor.getConfiguredColor(SplashScreenProgressMonitor.java:268)
at com.bc.ceres.core.runtime.internal.SplashScreenProgressMonitor.getConfiguredSplashProgressBarColor(SplashScreenProgressMonitor.java:259)
at com.bc.ceres.core.runtime.internal.SplashScreenProgressMonitor.<init>(SplashScreenProgressMonitor.java:91)
at com.bc.ceres.core.runtime.internal.SplashScreenProgressMonitor.createProgressMonitor(SplashScreenProgressMonitor.java:68)
at com.bc.ceres.core.runtime.RuntimeFactory.createProgressMonitor(RuntimeFactory.java:79)
at com.bc.ceres.core.runtime.RuntimeFactory.createRuntime(RuntimeFactory.java:50)
at com.bc.ceres.core.runtime.RuntimeLauncher.launch(RuntimeLauncher.java:25)
... 6 more


In the debugger I can follow what happens until com.bc.ceres.launcher.Launcher.launch(Launcher.java:99). The debugger shows that the runtimeConfig file (config/beam.config) is correctly loaded. This is its content:

1beam.home = .
2beam.app = VisatMain
3beam.logLevel = ALL
4beam.debug = true
5beam.splash.image = ./src/main/bin/common/splash.png



What I want to do is to develop a new BEAM Processor / Visat Plugin. Do I need to go through all this or are there simpler/faster ways to proceed. The developer documentation is a bit unclear since the 4.x version.

Thanks,
Reinoud Bokhorst
Flag Flag
RE: Launcher error
11/18/09 1:49 PM as a reply to R Bokhorst.
Dear Reinoud,

you've hit a problem in the configuration parsing. I've fixed this and committed it to subversion. Please update.

Have you seen the BEAM 4 Programming Tutorial in the wiki ?

Best regards,
Marco Zuehlke
Flag Flag
RE: Launcher error
11/19/09 5:17 PM as a reply to Marco Zühlke.
Thanks, it works!
Yes, I saw the programming tutorial shortly after my post. I am well on my way now.

Regards,
Reinoud
Flag Flag

 

Welcome to the BEAM Forum!

We encourage you to sign in our forum and participate in the BEAM community. The forum is maintained by the BEAM project team who will most likely answer your questions within 24 hours (except during common holidays) - if not done by other community members. Collaborate, share your knowledge and learn from other users!

If you don't find what you are looking for, please also consider the following external forums: