Re: NPE at startup of my woapps (again)

From: Chuck Hill (chil..lobal-village.net)
Date: Fri Aug 21 2009 - 12:14:03 EDT

  • Next message: Nicolas Daniels: "Re: NPE at startup of my woapps (again)"

    On Aug 21, 2009, at 5:43 AM, Nicolas Daniels wrote:

    > Is it wobuild.properties or wolips.properties ?

    wobuild.properties is obsolete and not read. wolips.properties is the
    file. I don't recall where that is stored on Windows.

    Chuck

    > Anyway I tried both and it doesn't change anything.
    >
    > Here is the content of my wobuild.properties file:
    >
    > #This file stores the wo specific properties
    > #Wed Aug 19 09:43:07 CEST 2009
    > wo.wosystemroot=C:/Apple
    > wo.wolocalroot=C:/Apple
    > wo.woroot=C:/Apple
    > wo.system.root=C:/Apple
    >
    > I've set both wo.wosystemroot and wo.system.root properties because
    > I don't which one is the appropriate one.
    > I can put anything in this file (even something totally wrong to
    > make it failed) without any change. Thus it seems it doesn't read it
    > at all, or the exception is thrown before.
    >
    > I've also set the NEXT_ROOT environment variable.
    >
    > The weird thing is that the launch work fine with the wolips version
    > 3.3.5640 (but wod editor is not working with this version)
    >
    >
    >
    > Mike Schrag wrote:
    >> specifically the "wo.system.root" property
    >>
    >> On Aug 21, 2009, at 4:22 AM, Nicolas Daniels wrote:
    >>
    >>> Thanks Mike and Chuck for your answer, it sounds logical to use
    >>> eclipse 3.4 with wolips 3.4, unfortunately it doesn't solve the
    >>> problem.
    >>>
    >>> I'm now using Eclipse 3.4.2 with wolips 3.4.5915 (tried also with
    >>> 3.4.5830) and I've the same error at my application startup
    >>> (except for some code line number in the stack):
    >>>
    >>> java.lang.NullPointerException
    >>> at
    >>> org
    >>> .objectstyle
    >>> .wolips
    >>> .jdt
    >>> .classpath
    >>> .model.EclipseDependency.getSystemRoot(EclipseDependency.java:63)
    >>> at
    >>> org
    >>> .objectstyle
    >>> .woenvironment.frameworks.Dependency.isAppleProvided(Unknown Source)
    >>> at
    >>> org
    >>> .objectstyle
    >>> .woenvironment
    >>> .frameworks.DependencyOrdering.orderDependencies(Unknown Source)
    >>> at
    >>> org
    >>> .objectstyle
    >>> .wolips
    >>> .launching
    >>> .classpath
    >>> .WORuntimeClasspathProvider
    >>> .resolveClasspath(WORuntimeClasspathProvider.java:112)
    >>> at
    >>> org
    >>> .eclipse
    >>> .jdt
    >>> .internal
    >>> .launching
    >>> .RuntimeClasspathProvider
    >>> .resolveClasspath(RuntimeClasspathProvider.java:60)
    >>> at
    >>> org
    >>> .eclipse
    >>> .jdt
    >>> .launching.JavaRuntime.resolveRuntimeClasspath(JavaRuntime.java:
    >>> 1187)
    >>> at
    >>> org
    >>> .eclipse
    >>> .jdt
    >>> .launching
    >>> .AbstractJavaLaunchConfigurationDelegate
    >>> .getClasspath(AbstractJavaLaunchConfigurationDelegate.java:417)
    >>> at
    >>> org
    >>> .objectstyle
    >>> .wolips
    >>> .launching
    >>> .delegates
    >>> .WOJavaLocalApplicationLaunchConfigurationDelegate
    >>> .getClasspath
    >>> (WOJavaLocalApplicationLaunchConfigurationDelegate.java:125)
    >>> at
    >>> org
    >>> .eclipse
    >>> .jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:71)
    >>> at
    >>> org
    >>> .eclipse
    >>> .debug
    >>> .internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:
    >>> 764)
    >>> at
    >>> org
    >>> .eclipse
    >>> .debug
    >>> .internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:
    >>> 614)
    >>> at
    >>> org
    >>> .eclipse
    >>> .debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:
    >>> 865)
    >>> at org.eclipse.debug.internal.ui.DebugUIPlugin
    >>> $8.run(DebugUIPlugin.java:1068)
    >>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    >>>
    >>> I tried with the stable and the nightly, behavior is the same...
    >>> I also tried with a new project in a new workspace, no change.
    >>>
    >>> Config reminder:
    >>> Eclipse 3.4.2 - WOLips/M2Eclipse
    >>> JDK 1.6 update 16 (64 bits)
    >>> OS: Win VISTA 64 bits Ultimate
    >>>
    >>> Thanks for any idea...
    >>>
    >>> Nicolas
    >>>
    >>> Chuck Hill wrote:
    >>>> On Aug 20, 2009, at 9:01 AM, Nicolas Daniels wrote:
    >>>>
    >>>>> Hmmm, I had some problems with my mails yesterday, I don't know
    >>>>> if my send worked, so I send it again, sorry if you have already
    >>>>> received it.
    >>>>>
    >>>>> -->
    >>>>>
    >>>>> Hi all,
    >>>>>
    >>>>> I have freshly installed Eclipse 3.5.0 with WOLips stable build
    >>>>> 3.4.5924
    >>>>
    >>>> WOLips 3.4.x is for Eclipse 3.4.x, you need WOLips 3.5.x
    >>>> versions. Or, better, use Eclipse 3.4 as the Eclipse 3.5 support
    >>>> in WOLips is not yet 100% tested/done/happy.
    >>>>
    >>>>
    >>>> Chuck
    >>>>
    >>>>
    >>>>
    >>>>> (from the update site) and I can't get my WO-apps to start.
    >>>>> Every timeI launch a WOApp, I get the following error:
    >>>>>
    >>>>> java.lang.NullPointerException
    >>>>> at
    >>>>> org
    >>>>> .objectstyle
    >>>>> .wolips
    >>>>> .jdt
    >>>>> .classpath
    >>>>> .model.EclipseDependency.getSystemRoot(EclipseDependency.java:63)
    >>>>> at
    >>>>> org
    >>>>> .objectstyle
    >>>>> .woenvironment.frameworks.Dependency.isAppleProvided(Unknown
    >>>>> Source)
    >>>>> at
    >>>>> org
    >>>>> .objectstyle
    >>>>> .woenvironment
    >>>>> .frameworks.DependencyOrdering.orderDependencies(Unknown
    >>>>> Source)
    >>>>> at
    >>>>> org
    >>>>> .objectstyle
    >>>>> .wolips
    >>>>> .launching
    >>>>> .classpath
    >>>>> .WORuntimeClasspathProvider
    >>>>> .resolveClasspath(WORuntimeClasspathProvider.java:112)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .jdt
    >>>>> .internal
    >>>>> .launching
    >>>>> .RuntimeClasspathProvider
    >>>>> .resolveClasspath(RuntimeClasspathProvider.java:60)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .jdt
    >>>>> .launching.JavaRuntime.resolveRuntimeClasspath(JavaRuntime.java:
    >>>>> 1205)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .jdt
    >>>>> .launching
    >>>>> .AbstractJavaLaunchConfigurationDelegate
    >>>>> .getClasspath(AbstractJavaLaunchConfigurationDelegate.java:417)
    >>>>> at
    >>>>> org
    >>>>> .objectstyle
    >>>>> .wolips
    >>>>> .launching
    >>>>> .delegates
    >>>>> .WOJavaLocalApplicationLaunchConfigurationDelegate
    >>>>> .getClasspath
    >>>>> (WOJavaLocalApplicationLaunchConfigurationDelegate.java:125)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:
    >>>>> 71)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .debug
    >>>>> .internal
    >>>>> .core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .debug
    >>>>> .internal
    >>>>> .core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
    >>>>> at
    >>>>> org
    >>>>> .eclipse
    >>>>> .debug
    >>>>> .internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
    >>>>> at
    >>>>> org.eclipse.debug.internal.ui.DebugUIPlugin
    >>>>> $8.run(DebugUIPlugin.java:1069)
    >>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    >>>>>
    >>>>> My environment variables NEXT_ROOT and NEXT_SYSTEM_ROOT are set.
    >>>>>
    >>>>> I have tried to delete my launch config and recreate it without
    >>>>> any
    >>>>> change. I've also tried to create a new empty WOProject, and the
    >>>>> same
    >>>>> error occurred.
    >>>>> This is also happening with the today wolips nightly build.
    >>>>>
    >>>>> If I use the wolips version 3.3.5640, my wo application can
    >>>>> start but
    >>>>> the WOD/Html view is not working anymore (which seems to be
    >>>>> normal with
    >>>>> this eclipse version).
    >>>>>
    >>>>> My configuration:
    >>>>> Eclipse 3.5.0 - WOLips/M2Eclipse
    >>>>> JDK 1.6 update 16 (64 bits)
    >>>>> OS: Win VISTA 64 bits Ultimate
    >>>>>
    >>>>> Any ideas?
    >>>>>
    >>>>>
    >>>>> Thanks,
    >>>>> Nicolas
    >>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>
    >>
    >>
    >
    >

    -- 
    Chuck Hill             Senior Consultant / VP Development
    

    Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects



    This archive was generated by hypermail 2.0.0 : Fri Aug 21 2009 - 12:15:16 EDT