Maybe TransientComposite is not so bad as a name.
Maybe CompositeContext should be explicitely named ThreadLocalComposite?
Niclas Hedhman a écrit :
On Mon, Jun 4, 2012 at 5:13 AM, Tibor Mlynarik<[email protected]> wrote:
POJO can't have modifiers and mixins ( nor if it is interface )
Well, right now it can't, but we have been considering it, provided
that the POJO and its methods are not final.
into POJO can be injected: @Service, @Structure, another POJO via
@Uses, transient via @Uses
POJO can be injected into Transient, another POJO
Transients supports exactly the same injections and fragments as the
other composites + @Uses.
POJOs (via ObjectFactory) supports all injections, but currently not
any fragments.
is there documentation for this DI posibilites ?
Not really a comparison between the two, or where the differences
between all are listed. "Objects" has relatively little documentation.
Another unknown thing, which is kind of a "Composite" that is
practically undocumented, is called CompositeContext (probably bad
name), which is a TransientComposite with a ThreadLocal scope. That
thing doesn't support @Uses...
Cheers
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
