-
1. Re: Some kind of outjection
pmuir Apr 6, 2009 3:24 PM (in response to diegocoronel)You can use producer fields as a kind of outjection for sure.
You can certainly use events to update injections (e.g. using @Obtains Instance<Foo>
-
2. Re: Some kind of outjection
hajdi Apr 6, 2009 4:43 PM (in response to diegocoronel)What is the reason why WebBeans don't have outjection? Not that I would like it to have. In fact I hesitate to use them in Seam.
-
3. Re: Some kind of outjection
pmuir Apr 6, 2009 4:49 PM (in response to diegocoronel)Personally, I'm not a huge fan of outjection, and to me, Web Beans provides the right point to remove this feature, which (again IMO) experience has shown isn't that useful.
-
4. Re: Some kind of outjection
gonorrhea Apr 6, 2009 5:04 PM (in response to diegocoronel)
Pete Muir wrote on Apr 06, 2009 16:49:
Personally, I'm not a huge fan of outjection, and to me, Web Beans provides the right point to remove this feature, which (again IMO) experience has shown isn't that useful.So is outjection (which is 1/3 of bijection), now an anti-pattern, so to speak?
I've used outjectin a lot in my code using @Out in Seam apps... Is the problem due to the fact that the HttpSession gets bloated with objects when you continually outject to session and/or conversation contexts?
what's a concrete example of oujection in WebBeans?
the difference b/n producer and events?
-
5. Re: Some kind of outjection
pmuir Apr 7, 2009 2:58 PM (in response to diegocoronel)
Arbi Sookazian wrote on Apr 06, 2009 17:04:
Pete Muir wrote on Apr 06, 2009 16:49:
Personally, I'm not a huge fan of outjection, and to me, Web Beans provides the right point to remove this feature, which (again IMO) experience has shown isn't that useful.
So is outjection (which is 1/3 of bijection), now an anti-pattern, so to speak?It's not an anit-pattern IMO, but I would always use it as an optimization, not part of the base design for the app.
I've used outjectin a lot in my code using @Out in Seam apps... Is the problem due to the fact that the HttpSession gets bloated with objects when you continually outject to session and/or conversation contexts?
No, for me the problem is it produces apps in which the wiring can be harder to understand.
what's a concrete example of oujection in WebBeans?
the difference b/n producer and events?@Produces @Foo Bar bar;
Read the spec ;-)