[bv-dev] bv-dev] [BVAL-251] Improve Bean Validation support for modularized environments

[Emmanuel Bernard]

On 14 mai 2012, at 17:19, Hardy Ferentschik wrote:

>>>>> 
>>>>> From where:
>>>> 
>>>> - from the user application or from the module depending on BV
>>> 
>>> I am also trying to understand what a modular environment means for a shared ValidatorFactory.
>>> If a user application depends on BV and also uses custom constraints, does it not mean the application 
>>> would need to build its own ValidatorFactory via ValidatorFactory#usingContext()#classLoaderService(classLoaderService).
>> 
>> That would sucks balls!
> 
> How else do you ensure class visibility (mind you I am just trying to understand how these environments work)

I'm unclear too. I wish to OSGi semi-gods would step in. But I imagine that OSGi imposing these string would lead to a custom way to initialize the ValidatorFactory. Some kind of bootstrapper class at the module level would have to be implemented to wire things up together. The bootstrapper class would be responsible from providing the ClassloaderService impl as well as ConstraintValidatorFactory etc.

As I said that's guesstimate on my part but every time I tried to ask this question, people started to walk the other direction or for the bravest going full stream theoretical and conceptual ;)