[
https://issues.jboss.org/browse/WFLY-409?page=com.atlassian.jira.plugin.s...
]
Hardy Ferentschik commented on WFLY-409:
----------------------------------------
{quote}
Is this to say that in applications with multiple persistence units a validator factory is
created for each PU? If so, I don't think that's neccessary as I'm not aware
of any PU-specific configuration related to validation.
{quote}
That's right. Maybe I am just not sure what this issue stands for.
{quote}
Instead the same VF can be used for all the PUs of one application which will save
memory.
{quote}
Right
{quote}
But with WFLY-1705 done, this should actually be the case, i.e. JPA consistently uses the
one and only (in the context of one application) LazyValidatorFacotry (I think that's
what Scott is saying).
{quote}
If this is the case, I am fine. Then I just need to find out why my test case ( see
[
HV-837|https://hibernate.atlassian.net/browse/HV-837]) is not working.
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