I noticed JSF 2.2 canceled the DI in JSF components in final Specs, only support in JSF backend beans.
MyFaces CODI provides @Advanced for DI in non contextual object...it is still useful for JSF 2.2...but I do not want to add this to enable injection on JSF validator, converter, etc. Hantsy On 6/1/2013 22:11, Thomas Andraschko wrote: > Also if BV 1.1 is coming soon, many customers can't upgrade to BV 1.1 or > JavaEE 7 the next 1-2 years. > So IMO it would be a great feature which shoudl be disabled per default. > > > 2013/6/1 Romain Manni-Bucau <rmannibu...@gmail.com> > >> Idem, not blocking IMO and bval 1.1 is coming so would be useless soon >> Le 1 juin 2013 15:56, "Gerhard Petracek" <gerhard.petra...@gmail.com> a >> écrit : >> >>> hi john, >>> >>> codi doesn't do auto registration. you need @Advanced to enable it. >>> >>> if you aren't allowed to use bv 1.1 right know, you can just use >>> BeanProvider manually (usually there are just few constraint-validators >>> which need it at all) >>> or keep what your are using now in parallel or just copy those few >> classes >>> to your ee6 (only) project. at least in case of codi they are quite >>> independent (and in most cases just simple wrappers). -> -1 for adding >> it. >>> regards, >>> gerhard >>> >>> >>> >>> 2013/6/1 John D. Ament <john.d.am...@gmail.com> >>> >>>> Hi All >>>> >>>> I wanted to begin introducing some level of BeanValidation Support. >> The >>>> main goal that I have is to be able to create CDI aware constraint >>>> validators, let's say you want to validate @NonExistentEmail then you >>>> should be able to run a query against your DB using your CDI services >> and >>>> determine if the given email is already present or not. >>>> >>>> To do this, both Seam3 and CODI introduced a CDI aware >> ConstraintFactory. >>>> When it creates an instance the instance is a CDI object, so it has >> full >>>> access to @Inject fields. I'd like to bring this type of functionality >>>> over to DS. >>>> >>>> The point where the two diverge is that CODI does an auto registration >>>> whereas Seam3 does a registration via validation.xml. As far as I >> know, >>>> CDI already allows the injection of Validator and ValidatorFactory >>> (though >>>> the OWB guys can tell me if they disagree). >>>> >>>> Please let me know if anyone has concerns with adding this. Yes, I >>> realize >>>> that this functionality is in bean val 1.1, but not everyone can >> upgrade >>> to >>>> bean val 1.1 yet. >>>> >>>> John >>>> -- Hantsy Bai Blog:http://hantsy.blogspot.com LinkedIN:http://www.linkedin.com/in/hantsy
