Re: WOLips 1.1.0.82 beta 3, Principle Class, and ApplicationClass

From: ulrich köster (ulric..bjectstyle.org)
Date: Mon Aug 23 2004 - 13:09:41 EDT

  • Next message: ulrich köster: "Re: run WO with parameter"

    hi,

    the difference between 1.* and 1.1:

    WOLips 1.1 stores the principal class in the build.properties. The new
    build.xml takes the value from the build.properties for the principal class.

    Ulrich
    ----- Original Message -----
    From: <Pierre.Bernar..cl.lu>
    To: <brenda..lickspace.com>; <ulrich@objectstyle.org>;
    <woproject-de..bjectstyle.org>
    Sent: Monday, August 23, 2004 9:33 AM
    Subject: RE: WOLips 1.1.0.82 beta 3, Principle Class, and ApplicationClass

    Hi!

    I am still running Eclipse 2.1.1 with an older version of WOLips. Thus I
    can't give definitive answers about the new beta.

    The notion of Principal Class however is a WebObjects one. A bundle
    (framework or application) may have a principal class. That class is touched
    when the bundle is loaded. Thus static initializers in that class get a
    chance to initialize other classes of the bundle before they get used. Refer
    to the NSBundle documentation for mor information.

    In the version of WOLips I am running the application class name is set by
    an argument to the <woapplication> task in the build.xml file. Oddly enough
    that argument is called "principalClass" which is the same name as the one
    used to set the principal class on a framework.

    Pierre

    -----Original Message-----
    From: Brendan Duddridge [mailto:brenda..lickspace.com]
    Sent: Sunday, August 22, 2004 9:35 PM
    To: Ulrich Köster; WOLips <woproject-de..bjectstyle.org>
    Subject: WOLips 1.1.0.82 beta 3, Principle Class, and ApplicationClass

    I'm wondering what the new fields on the WOLips Build panel are for?

    I thought maybe Principal Class field would set the ApplicationClass of the
    MacOSClassPath.txt file to whatever I typed in there.

    For example, my Application class is in a package called
    com.clickspace.driveit.diadmin, so I put
    com.clickspace.driveit.diadmin.Application in the Principle Class field and
    then I did an Install build of my application using the WOLips Install
    command.

    Looking in the MacOSClassPath.txt file of my installed directory, I see the
    ApplicationClass is still set as follows:

    # ApplicationClass == Application

    I guess the Principle Class isn't used for this.

    So, what would be used to automatically set the ApplicationClass of the
    MacOSClassPath.txt file (and the UNIXClassPath.txt file too as we also
    deploy to Solaris) at install time?

    Thanks,

    ___________________________

    Brendan Duddridge

    ClickSpace Interactive Inc.
    Suite L100
    239 - 10th Ave SE
    Calgary, AB T2G 0V9
    Canada
    (403) 277-5591
    http://www.clickspace.com/

    **********************************************************************
    This email and any files transmitted with it are intended solely for
    the use of the individual or entity to whom they are addressed.
    If you have received this email in error please notify the sender
    of this message. (Pierre.Bernar..cl.lu)
    This email message has been checked for the presence of computer
    viruses; however this protection does not ensure this message is
    virus free.
    Banque centrale du Luxembourg; Tel ++352-4774-1; http://www.bcl.lu
    **********************************************************************



    This archive was generated by hypermail 2.0.0 : Mon Aug 23 2004 - 13:16:26 EDT