Re: [seam-dev] is there an equivalent of Seam 2 @out in CDI / Seam 3

Thanks for the douse I'm going to test this right away. Antoine Sabot-Durand Le 16 mars 2011 à 18:29, Dan Allen <dan.j.allen(a)gmail.com&gt; a écrit : You can create a producer that aliases a name to a property, like this: @Produces @Named public Hotel getHotel() { return booking.getHotel(); } #{hotel} You can also use a producer field, like so: @Produces @Named private Hotel hotel; #{hotel} Produces sort of turns outjection on it's head. But if you think about it, it's a better way to go about it because it's more robust to read the state of the model as it is, then try to shift the information around into variables from which to read them, as outjection did. What you can't do is use the same variable name to refer to state on two different models, unless of course your producer method does some conditional logic (saying if this screen, give this result, if this screen, give a different result). But again, that's a good thing because then tooling can actually tell you where the data is coming from. This is a key topic for the migration guide. Feel free to contribute examples of how you might solve an outjection scenario with produces. It's a good exercise anyway. -Dan On Wed, Mar 16, 2011 at 13:03, Ken Finnigan <ken(a)kenfinnigan.me&gt; wrote: -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://www.google.com/profiles/dan.j.allen#about http://mojavelinux.com http://mojavelinux.com/seaminaction