OK I've added WeldContainer, so now it's as Emmanuel suggested:
WeldContainer weld = new Weld().initialize();
new Weld().event() // doesn't exist
new WeldContainer(InstanceManager, BeanManager) // is package protected
On 30/11/2009, at 9:12 AM, Peter Royle wrote:
I've done the first iteration of this (checked in - r5173). It doesn't yet
separate out the initialisation, I'll do that next.
One problem is that I can't get the following line to compile:
org/jboss/weld/environment/se/test/WeldMainTest.java:[70,18] cannot find symbol
symbol : method
location: interface javax.enterprise.inject.Instance<javax.enterprise.event.Event>
I think the problem is that my CustomEvent doesn't implement or extend Event. I
don't think it has to though (am I mistaken?). Anyone know what I'm missing?
On 24/11/2009, at 11:11 PM, Dan Allen wrote:
> > WeldContainer weld = new Weld().initialize();
> > weld.instance().select(Foo.class).get();
> Yes, this seems sensible to me, as it will allow us to provide flexibility with the
configuration in the future.
> Emmanuel, master of fluent APIs, has made an important point that we should keep in
mind when designing a sequential call chain. Think twice before returning "this"
and think if there is a more specific type that you can return that narrows the options
based on where you are in the sequence. That way, you prevent being able to invoke methods
out of sequence.
> You can now prevent:
> new Weld().event()
> Returning a more specific type is also self documenting.
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
> weld-dev mailing list
weld-dev mailing list