Re: Build problems for Windows

From: Chuck Hill (chil..lobal-village.net)
Date: Thu Nov 01 2007 - 20:43:33 EDT

  • Next message: timc..pg.com.au: "Re: Build problems for Windows [Solved]"

    That sounds like a classpath problem, it is picking up some other
    Main.java. You can try this as a diagnostic:

    Class mainClass = _NSUtilities.classWithName("Main");
    NSLog.out.appendln("Main class is " + mainClass.getClass().getName());

    That may provide a clue.

    Chuck

    On Nov 1, 2007, at 5:34 PM, timc..pg.com.au wrote:

    > And I forgot to mention, my current build environment which didn't
    > work
    > is eclipse 3.3.1.1 and wolips 3.3.4574
    >
    > Tim
    >
    > Quoting timc..pg.com.au:
    >
    >> I have a Windows deployment server running webobjects 5.2.4. I just
    >> updated the Wonder frameworks from 3.405 to 4.061. Then when I
    >> restarted my webobjects apps, an app that was built one month ago
    >> started fine, but an app built last week didn't. It gave the error
    >>
    >> Application: Testlink
    >> Error: java.lang.IllegalArgumentException: Class 'Main' exists but
    >> is
    >> not a subclass of WOComponent.
    >> Reason: <com.webobjects.appserver._private.WOComponentDefinition>
    >> Class
    >> 'Main' exists but is not a subclass of WOComponent.
    >> Stack trace:
    >> File Line# Method Package
    >> WOComponentDefinition.java 414 _componentClass
    >> com.webobjects.appserver._private
    >> WOComponentDefinition.java 422 componentClass
    >> com.webobjects.appserver._private
    >> WOComponentDefinition.java 428 _componentInstanceInContext
    >> com.webobjects.appserver._private
    >> WOComponentDefinition.java 573 componentInstanceInContext
    >> com.webobjects.appserver._private
    >> WOApplication.java 1954 pageWithName com.webobjects.appserver
    >> WOComponentRequestHandler.java 273 _dispatchWithPreparedSession
    >> com.webobjects.appserver._private
    >> WOComponentRequestHandler.java 322 _dispatchWithPreparedApplication
    >>
    >> com.webobjects.appserver._private
    >> WOComponentRequestHandler.java 358 _handleRequest
    >> com.webobjects.appserver._private
    >> WOComponentRequestHandler.java 432 handleRequest
    >> com.webobjects.appserver._private
    >> WOApplication.java 1306 dispatchRequest com.webobjects.appserver
    >> ERXApplication.java 1155 dispatchRequest er.extensions
    >> WOWorkerThread.java 173 runOnce com.webobjects.appserver._private
    >> WOWorkerThread.java 254 run com.webobjects.appserver._private
    >> Thread.java NA run java.lang
    >> NA : Non applicable, JIT activated
    >>
    >> I have been using the latest wolips and eclipse versions, but I
    >> can't
    >> remember exactly which ones they were on 10th October 2007 when it
    >> last
    >> worked but I think it was wolips 3.3.4395 on eclipse 3.3.1
    >>
    >> I rebuilt last weeks app using an old copy of eclipse 3.3 running
    >> wolips
    >> 3.3.4252 and it started without problem on the Windows deployment
    >> server.
    >>
    >> Note that I am building on Mac OS X 10.4.10 with webobjects 5.3.3
    >> installed. Both Windows and Mac are using Java 1.5.0.
    >>
    >> Hopefully this is something that can be fixed otherwise I will have
    >> to
    >> keep my old version of eclipse for doing final builds.
    >>
    >> Tim Cummings
    >>
    >>
    >>
    >
    >
    >

    -- 
    

    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 : Thu Nov 01 2007 - 20:45:08 EDT