Re: ClassPath Order (NewHotness)

From: Kieran Kelleher (kieran_list..ac.com)
Date: Mon Sep 08 2008 - 23:55:01 EDT

  • Next message: Guillaume Polet: "Re: Hotness library location on Windows"

    Yes, moving ERExtensions above WOOgnl works for the EXExtensions
    generics patches getting in front of WO. I would never have guessed
    that one!

    It definitely might be worthwhile to always push ERExtensions to the
    top of the classpath stack since that is where the patches and class
    substutions are.

    Thanks, Kieran

    On Sep 8, 2008, at 8:47 PM, Mike Schrag wrote:

    >> If I add ERExtensions to a project and push it above WebObjects, it
    >> still tells me that NSArray is not generic. However, if I just add
    >> ERExtensions as Projects (because I have them linked to my
    >> workspace), and push the projects above WO Frameworks, the
    >> ERExtensions generics NSArray, etc are picked up and errors go
    >> away ......
    > Hmm .. if you push ERExtensions framework up above WOOgnl, does it
    > fix the problem? This is a tricky thing and related to the depth
    > first vs breadth first stuff. If WOOgnl depends on WO, then WO will
    > end up loading (transitively) in eclipse before ERX, and therefore
    > will not be generic. If you push ERX up above it, it will win. I
    > should make the reordering thing explicitly push ERX up to the first
    > item in the wonder libs list as part of the conversion .... This is
    > really only an issue because ERX actually overrides classes in WO.
    > If packages were non-overlapping, this wouldn't be nearly as much of
    > an issue.
    >
    > ms
    >


    Properties_for_FileUpload-1.jpg

    This archive was generated by hypermail 2.0.0 : Mon Sep 08 2008 - 23:55:59 EDT