Re: NPE at startup of my woapps

From: Guillaume Polet (guillaumedenal..mail.com)
Date: Mon Feb 23 2009 - 03:33:48 EST

  • Next message: Q: "Re: wocomponent wizard preview"

    Hi,

    I haven't had to time to go to the nightly build yet.
    My installation was a fresh install working on an existing workspace
    that I was using with Eclipse 3.3.2 (and a previous version of WOLips).
    I did not change anything to my launch configurations when switching
    from 3.3.2 to 3.4.1.
    I tried today to delete all my WOApplication launch configuration and
    recreate them from scratch but it does not work either. My launch
    configurations are quite straight forward: I only change the heap space
    and the WOPort, everything else is the default config (with the
    classpath coming from Maven).

    Part of the reasons why I updated Eclipse, is that M2Eclipse was
    screwing over and over my launch configurations and it seems that
    updating their plugin would fix it (forcing me to go to 3.4.1).

    Any thoughts? Would the nightly build fix this issue?

    Thanks,

    Guillaume

    Lachlan Deck a écrit :
    > Hi there,
    >
    > On 20/02/2009, at 12:12 AM, Guillaume Polet wrote:
    >
    >> Yes indeed, I'm using the stable build (or at least the one retrieved
    >> from the stable url, build #3.4.5679). Unfortunately I could not find
    >> any more recent build on the nightly server. Is this the correct url
    >> for nightly: http://webobjects.mdimension.com/wolip 3.s/nightly/ ?
    >>
    >> The only features I haven't installed are:
    >> * WOLips Apple Maven Integration (since I'm on Windows, I guess I
    >> must skip this one)
    >
    > Not dependent on Apple OS - but m2eclipse btw.
    >
    >>> My guess is that you're running the new stable build and not
    >>> nightly? Is it possible you're missing wolips.properties? Can you
    >>> try grabbing the latest nightly and restart eclipse and see if your
    >>> problem goes away?
    >
    > Interestingly I saw this yesterday a few times on my collegues machine
    > whilst trying to get it working and we're using nightly.
    >
    > I *think* it had to do with a borked launch configuration or classpath
    > variables as the wolips.properties was certainly there. That's a bit
    > vague sorry.
    >
    > Is this for a fresh / old workspace? Did you copy a launch configuration?
    >
    >>>> java.lang.NullPointerException
    >>>> at
    >>>> org.objectstyle.wolips.launching.delegates.WOJavaLocalApplicationLaunchConfigurationDelegate.getProgramArguments(WOJavaLocalApplicationLaunchConfigurationDelegate.java:224)
    >>>>
    >>>> at
    >>>> org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:63)
    >>>>
    >>>> 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:880)
    >>>>
    >>>> at
    >>>> org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1083)
    >>>>
    >>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    >>>>
    >>>> I have tried adding program arguments without any success. I also
    >>>> tried to delete my launch config and recreate it without any change.
    >>>>
    >>>> My configuration:
    >>>> Eclipse 3.4.1 J2EE- WOLips/M2Eclipse/Jadclipse/Veloeclipse/Cypal
    >>>> JDK 1.6 update 11
    >>>> OS: Win XP Pro
    >
    > with regards,
    > --
    >
    > Lachlan Deck
    >
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Mon Feb 23 2009 - 03:34:41 EST