[
https://issues.apache.org/jira/browse/OPENJPA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717266#action_12717266
]
Pinaki Poddar commented on OPENJPA-1114:
----------------------------------------
Can this vaalidator be configured per-EM basis or only per_EMF basis?
If it can only be done per-EMF basis then there should not be warning per EM.
PersistenceProductDerivation constructs ValidatingLifecycleEventManager.
This is an unusual usage of plug-in. Can you elaborate why
ValidatingLifecycleEventManager can not be plugged-in in the usual way other
plug-ins work?
There are many plug-ins for which compile-time dependency to a third-party
library is avoided.
> Bean Validation APIs should be an optional runtime dependency
> -------------------------------------------------------------
>
> Key: OPENJPA-1114
> URL: https://issues.apache.org/jira/browse/OPENJPA-1114
> Project: OpenJPA
> Issue Type: Sub-task
> Components: validation
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0-M2
>
> Attachments: OPENJPA-1114.patch, OPENJPA-1114.patch
>
>
> Bean Validation APIs should be an optional runtime dependency by using
> reflection to determine if the APIs are available before accessing our
> ValidatorImpl class or any javax.validation.* API classes.
> openjpa-persistence will set scope=provided on geronimo-validation_1.0_spec
> openjpa-all will include the spec in the aggregated all jar
> openjpa-persistence-jdbc will not add a test dependency on the spec
> openjpa-integration will be used to test the validation support via
> OPENJPA-1106
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
