[ https://issues.apache.org/jira/browse/OPENJPA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717247#action_12717247 ] 

Donald Woods commented on OPENJPA-1114:
---------------------------------------

The warning happens everytime you create a new EM/BrokerImpl, as a new LifecycleEventManager gets created for each Broker created.
If we decide later on to include the BV API from Geronimo as a runtime dependency in the POMs (currently it is not, but we include it in the release assembly and openjpa-all.jar) then we can change that log msg to a Trace, but for now, we should include the warning since it is an optional depend (which means a user should supply their own API + Impl for now.)


> 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.