[
https://issues.apache.org/jira/browse/BVAL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416645#comment-15416645
]
Romain Manni-Bucau commented on BVAL-145:
-----------------------------------------
Hmm, what is the issue setting the right classloader in OSGi? Always did it in
KarafEE and was working well. Only small issue i have with your proposal is it
introduces an OSGi hack in bval standalone part which is OSGi dependent - not
import but loader behavior like should the resource be prefixed by / or not
etc...
For me this belongs to bval boot in OSGi so maybe a bval-osgi.
Wdyt?
> BVal bundle fails to load resources under OSGi
> ----------------------------------------------
>
> Key: BVAL-145
> URL: https://issues.apache.org/jira/browse/BVAL-145
> Project: BVal
> Issue Type: Bug
> Components: jsr303
> Affects Versions: 1.1.1
> Environment: Karaf 4.0.5
> Reporter: Łukasz Dywicki
>
> Current logic of resource lookups in bval rely on context class loader and
> when it is not present it fallbacks to classloader which loaded bval. This
> works perfectly fine for most of cases, but fails under OSGi because TCCL in
> many cases is set to boot loader which contains no information about running
> modules. For this reason bval fails to load jsr303 mappings and always
> returns empty validation result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
