<div dir="ltr"><div>Any work on such features is something that cannot go into 11, as we are mostly at cut-off point with development.</div><div><br></div><div>Such work should target WildFly 12.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 13, 2017 at 10:50 AM, Gunnar Morling <span dir="ltr"><<a href="mailto:gunnar@hibernate.org" target="_blank">gunnar@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div><TL,DR>Should we update WildFly to BV 2.0 and Hibernate Validator 6.0, or should new modules be added for those, letting the user to choose the version to enable?</TL,DR></div><div><br></div><div>The Bean Validation 2.0 spec (JSR 380) is almost done [1], so I'd like to discuss how BV 2 and its reference implementation HV 6 can be integrated into WildFly. BV 2 will be part of Java EE 8.</div><div><br></div><div>I can think of two approaches:</div><div><br></div><div>1) Just updating the existing WildFly modules for BV API and HV to the new versions</div><div>2) Leave the existing modules for BV 1.1 (+ implementation) and add separate modules for BV 2.0</div><div><br></div><div>1) would be easier and less effort. But I'm not sure how feasible it is, in case that WF should remain Java EE 7 compatible for the time being. Also, while BV 2 is fully backwards compatible at the spec-level, Hibernate Validator amends the spec API with some extended functionality. In that extended HV-specific API some changes were required, mostly as previous experimental features were replaced by equivalent standardized functionality in the BV API.</div><div><br></div><div>2) would let the user chose between BV 1.1 and 2.0, but it'd entail some more work:</div><div><br></div><div>* A place for that configuration is required. I think it could be done similarly to JPA, i.e. via a property with the module name in META-INF/validation.xml</div><div>* Depending on that configuration, the right set of modules needs to be enabled. Several modules currently have a fixed dependency to the "org.hibernate.validator:main" module (e.g. JPA, Weld, JCA, RestEasy) which would have be made more dynamic, based on the version chosen by the user.</div><div><br></div><div>What does everyone think on this? And what could be a suitable WildFly target version for such change? Could we aim at incorporating BV 2.0 into WF 11?</div><div><br></div><div>Thanks,</div><div><br></div><div>--Gunnar</div><div><br></div><div>[1] <a href="http://beanvalidation.org/news/2017/07/12/bean-validation-2-0-cr3-submitted-to-final-approval-ballot/" target="_blank">http://beanvalidation.org/<wbr>news/2017/07/12/bean-<wbr>validation-2-0-cr3-submitted-<wbr>to-final-approval-ballot/</a></div><div><br></div></div>
<br>______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank" rel="noreferrer">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br></blockquote></div><br></div>