[
https://issues.jboss.org/browse/WFLY-409?page=com.atlassian.jira.plugin.s...
]
Hardy Ferentschik commented on WFLY-409:
----------------------------------------
[~smarlow], why was this issue closed? Also, I am not sure I am follwoing. The title says
{quote}
JPA should allow for a bean validator factory per persistence unit or per application
deployment
{quote}
and then in the summary you say:
{quote}
Currently, a new bean validator factory instance is associated with each deployed
persistence unit.
{quote}
Is there, or is there not a new {{ValidatorFactory}} per PU/application? There should be,
because each application could configure its own {{ValidatorFactory}} via
{{validation.xml}}.
JPA should allow for a bean validator factory per persistence unit or
per application deployment
------------------------------------------------------------------------------------------------
Key: WFLY-409
URL:
https://issues.jboss.org/browse/WFLY-409
Project: WildFly
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Reporter: Scott Marlow
Labels: open_to_community
Fix For: 8.0.0.Beta1
Currently, a new bean validator factory instance is associated with each deployed
persistence unit. This jira calls for adding a new PU property that specifies that a
'per app bean validator factory' should be used for a persistence unit (via a
persistence unit property).
This can be controlled by a new persistence unit property (see existing ones
[
here|https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide#JPARe...]).
The new property can be something like "org.jboss.as.jpa.shareValidatorFactory"
which defaults to false.
Look at
org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit() to
make this change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira