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@kenfinnigan.me> wrote:
If you want the result of @Produces to be EL accessible just throw a @Named on it.
Ken
Sent from my iPhone
For what I understand, it's not quite the same. I think it's more like @Factory, but I agree it's nearly the same and I could use it was possible to "Named" the "outjected" property in order to use it in EL...
Le 16 mars 2011 à 17:54, Ken Finnigan a écrit :
Antoine,
I'm pretty sure the equivalent for CDI is to use @Produces.
Ken
_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597