I love and use forClass="...". Please take a look at [1] below, when you get a chance to see all the chatter/discussion I had related to this topic. Sometime after this topic, I tried 'again' to use @Advanced and still didn't work. That is why I went with JSF @RequestScopedBeans that contain 'only' @FacesConverter forClass=...
[1] Migrating to CDI: injecting stateless/facade in Converter via facescontext<http://openejb.979440.n4.nabble.com/Migrating-to-CDI-injecting-stateless-facade-in-Converter-via-facescontext-td4658693.html> On Tue, Dec 4, 2012 at 10:51 PM, Gerald Turner <gtur...@unzane.com> wrote: > "Howard W. Smith, Jr." <smithh032...@gmail.com> writes: > > > I can confirm the same about CODI @Advanced not working in/with JSF > > @FacesConverter. My workaround (in a TomEE/CDI/MyFaces-CODI project) > > was to only add the @FacesConverter to JSF @RequestScoped managed > > beans, and they are working great in/with TomEE 1.5.1 SNAPSHOT. > > Thanks Howard, I'll probably go with that approach after more time > experimenting with @Advanced. > > Do you get to use the 'forClass' annotation attribute of > @FacesConverter, or do you have to link them by name (I forget the > mechanism, been spoiled by 'forClass'). > > -- > Gerald Turner Email: gtur...@unzane.com JID: gtur...@unzane.com > GPG: 0xFA8CD6D5 21D9 B2E8 7FE7 F19E 5F7D 4D0C 3FA0 810F FA8C D6D5 >
