[
https://issues.redhat.com/browse/WFLY-13734?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFLY-13734:
-----------------------------------------
{quote}
As I see it, we are introducing a non-EE-compatible server mode which I think is okay.
{quote}
Yes, Galleon layers allow you to provision a server that has what you want, and that
isn't necessarily spec compliant.
{quote}
I don't think we need to handle CALLBACK mode at all, as Hibernate will fail the
deployment for us.
{quote}
Sounds fine. I'll resolve this issue then.
JPA subsystem should fail deployment if ValidationMode.CALLBACK is
configured but the BV capability is not present
------------------------------------------------------------------------------------------------------------------
Key: WFLY-13734
URL:
https://issues.redhat.com/browse/WFLY-13734
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Brian Stansberry
Assignee: Scott Marlow
Priority: Major
This is a follow-on to
https://github.com/wildfly/wildfly/pull/13444 / WFLY-13726. That
fix is about applying logic consistently in both places where
PersistenceUnitServiceHandler integrates with BV. But I suspect the existing handling
isn't correct in the case where ValidationMode.CALLBACK is configured. The javadoc for
that enum value says "The persistence provider must perform the lifecycle event
validation. It is an error if there is no Bean Validation provider present in the
environment." But I think our handling is ignoring that if the BV capability is not
present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)