Re: Tighter EntityResolver

From: Mike Kienenberger (mkienen..mail.com)
Date: Fri Sep 30 2005 - 10:55:10 EDT

  • Next message: Mike Kienenberger: "Determining the DataMap for an ObjEntity when EntityResolver contains multiple maps"

    For cgen, it's

                entityResolver.addDataMap(additionalDataMaps[i]);

    So that's the only one that matters to me. I try to avoid doing weird
    things in runtime unless I'm writing unit tests :)

    On 9/30/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
    >
    > On Sep 30, 2005, at 12:13 AM, Mike Kienenberger wrote:
    >
    > > I'm not sure. Under what situations does the code get hit now? I'm
    > > most concerned as it relates to cross-DataMap resolution and mutlipel
    > > DataMaps.
    >
    > That's why I asked. It should work fine with multiple DataMaps, but
    > people could be doing weird things in runtime.
    >
    > E.g. dataMap.addObjEntity(myEntity) would've worked before, but now
    > whoever modified the DataMap would have to explicitly mark
    > EntityResolver as dirty. I think this is the only case that is
    > affected (this may affect the Modeler, but I am going to address it
    > internally).
    >
    > Andrus
    >

    This archive was generated by hypermail 2.0.0 : Fri Sep 30 2005 - 10:55:16 EDT