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 question is what to do instead. I *could* set these during assembly
instead, but then I would be required to have these instantiated just to
assemble the application, which is bad if I want to assemble it and they
view it using Envisage.
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.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
