hi harald, in codi that isn't supported out-of-the-box (intentionally). (fyi: basically it's allowed to cache the ValidatorFactory, but we also don't do it (intentionally).)
you can inject and cache it yourself easily. e.g. via a producer which exposes it as application scoped bean without qualifier (or a custom qualifier). for the integration with any other technology, you just have to resolve the cached version. e.g. in case of jsf2+ just replace the default-validator (with the id javax.faces.Bean). (or use the default integration via myfaces extval which is a bit more complex, because it's also compatible with jsf 1.x). regards, gerhard 2013/3/27 Harald Wellmann <hwellmann...@gmail.com> > I know this will be in Java EE 7 specs, but I guess Java EE 7 > implementations won't be ready for production before next year, so > there's a gap to be filled for projects using Java EE 6 for > production. That's why I'd like to see Bean Validation support in > DeltaSpike 0.5. > > I've had a look at the CODI implementation which looks pretty > straightforward to me - the only thing I don't see is how JSF picks up > the CDI-enabled ValidatorFactory instead of the default one. Is this > some magic in the CODI JSF module, or do you have to configure the > factory in META-INF/validation.xml? > > Best regards, > Harald > > > 2013/3/25 Gerhard Petracek <gerhard.petra...@gmail.com>: > > > > @ harald: > > java-ee7 is going to support it out-of-the-box. > > so we are discussing if and how we support it. > > (fyi: you can also copy it. you just need few classes which are pretty > > independent.) > > > > regards, > > gerhard >
