You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2015/12/14 14:08:46 UTC

[jira] [Commented] (SMX4-1618) Create javax.validation.api 1.1 spec bundle

    [ https://issues.apache.org/jira/browse/SMX4-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055955#comment-15055955 ] 

Christian Schneider commented on SMX4-1618:
-------------------------------------------

Not sure if this is necessary. It is quite common in OSGi that that methods to find implementations do not work. Like for example in the jpa case where the 
EntityManagerFactory is provided as a service. 

It is not expected that Persistence.createEntityManagerFactory works in OSGi. So I think we can go a similar way in OSGi. Either the project offering the ValidationProvider could register the service or we can have an adapter bundle. I am currently asking the question on the osgi-dev list to see if there is already a best practice or even an upcoming spec.

> Create javax.validation.api 1.1 spec bundle
> -------------------------------------------
>
>                 Key: SMX4-1618
>                 URL: https://issues.apache.org/jira/browse/SMX4-1618
>             Project: ServiceMix 4
>          Issue Type: Task
>          Components: specs
>            Reporter: Sergey Beryozkin
>            Assignee: Jean-Baptiste Onofré
>             Fix For: specs-2.4.0
>
>
> I believe 
> javax.validation.Validation#GetValidationProviderListAction#run and/or #loadProviders need to be made OSGI-friendly
> This is a regular dependency:
> {code:xml}
> <dependency>
>                 <groupId>javax.validation</groupId>
>                 <artifactId>validation-api</artifactId>
>                 <version>1.1.0.Final</version>
> </dependency>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)