On Tue, Sep 1, 2009 at 10:59 AM, Rickard Öberg<[email protected]> wrote: > Niclas Hedhman wrote: >> >> I have been working on QI-220 today, and it is about the inconsistent >> APIs for accessing the meta-info in various parts of the system. >> >> It is now being changed throughout to the following format; >> >> <T> T metaInfo( Class<T> infoType ); > > I have found a problem with this change. In StreamFlow I am assembling the > app first, and then immediately provide runtime instances of objects that I > need to expose as services. This is done by setting them as metadata in the > app, which I previously did using app.metaInfo().set(someobject);
> The above change is good, but now we need a new way to provide these kinds > of metainfo at the "between-assembly-and-runtime" stage. Yes, the problem is visible in the PluginTest as well, which I disabled, since I don't fully understand what the code was doing, but probably the same pattern as you have in StreamFlow. I am a bit busy with the JavaZone presentation today, but feel free to provide suggestions, and whether we need to have them inside 1.0... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
