We actually use Hibernate Validator extensions for core (i.e. non-Errai) stuff in TiMo and
IIRC even in quick starts.
e.g. @Email validation.
On 2012-06-13, at 6:53 PM, Jason Porter wrote:
I'm working on an example that will use DeltaSpike. I'm
looking at using
some Hibernate APIs (Envers, and some of the validators from Hibernate
Validator). Does anyone see a problem with this? The way I've thought
of jdf is not just to say here's how to do Java EE (which what we have
far better than what Oracle puts out), but also how we're extending the
platform and doing things that aren't part of the standard yet. Yes,
this ties you to our stuff, but in a way, isn't that what we want? We
want people to see what you can do with Java that is beyond the spec
using our stuff. Sure, you could stay with the standards and use only
the specs, but you can do so much more with some of the extras we
provide.
We have also done this with Errai in TicketMonster. I don't see this
being much of a problem.
_______________________________________________
jdf-dev mailing list
jdf-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jdf-dev