Re: WOLips (Eclipse 3.0.1) Linux Launch Classpath Problem

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Fri Dec 10 2004 - 13:11:21 EST

  • Next message: Ulrich Köster: "Re: webserver resources not found"

    Moin Ralf,

    some people use it on Linux.

    Are you able to launch a simple app from the command line?

    Is the NEXT_ROOT environment variable set?

    Ulrich

    Am 10.12.2004 um 18:13 schrieb Ralf Liebenow:

    > Hello !
    >
    > I installed the newest WOLips 1.1.0.90 into my Eclipse 3.0.1 and
    > created
    > a new Project (named X) using Framework (named Y).
    >
    > I can create classes and Resources, build them with ant (build.xml) and
    > deploy them, and the Application works OK.
    >
    > However, the launch Configuration I created to launch the Application
    > within Eclipse does not have the right Classpaths setup. NSBundle does
    > not find its Main Bundle because its X.woa Path is not in the
    > classpath.
    > It also does not find Resources for the Framework Y, because the
    > Y.framework Path is not in its classpath.
    >
    > The Framework is selected in the Java build Path of the Project (which
    > is necessary to compile the classes), and the jar-files are
    > referenced, so
    > the Problem is only in launching because application and frameworks
    > base
    > paths are not listed in the classpath at launch time (all the jar
    > files are).
    >
    > NSBundle uses the System Properties "java.class.path" and
    > "com.webobjects.classpath" to look for classes, Frameworks and
    > applications.
    >
    > "com.webobjects.classpath" is empty, when I launch in eclipse and
    > "java.class.path" lists only the necessary jar files, which is OK for
    > compilation, but for NSBundle the .framework and .woa Paths needed to
    > be
    > in there.
    >
    > I edited the Launch configuration and added the Variable
    > ${working_dir_loc_WOLips:X} to the classpath of the launch, and now
    > NSBundle
    > finds the main application bundle. But the frameworks are also missing
    > (and I don't want to maintain that list by hand, WOLips supported that
    > in
    > the older versions).
    >
    > The astonishing thing is, that the same Eclipse with the same Plugin
    > _and_
    > the same Project Files copied to a MacOSX machine worked flawlessly
    > without complaining, and without the need to add
    > ${working_dir_loc_WOLips:X}
    >
    > So what could be the cause here ? Is this a "linux only" matter ?
    >
    > Greetings
    > Ralf
    > --
    > theCode AG
    > Oranienstr. 10-11, 10997 Berlin [×]
    > fon +49 30 617 897-0 fax -10
    > ral..heCo.de http://www.theCo.de



    This archive was generated by hypermail 2.0.0 : Fri Dec 10 2004 - 13:11:40 EST