Hi Katya, we use this classloader when using the default provider so we want to be sure it is our default provider. If you specify the provider manually we are using the TCCL (line 97) so it should be ok.
Maybe try forcing the provider... The reason why we resetted the classloader like this when falling back to the default provider was to avoid to get OSGi issues. - Romain 2012/2/13 Katya Todorova <[email protected]> > Hi guys, > > While trying to run openEJB in OSGi, I came across an issue with > validator provider detection. It turned out that > org.apache.openejb.assembler.classic.ValidatorBuilder class uses its > own loader to look for available providers. > This causes problems when openEJB is not embedded in an application. > Shouldn't the ejb container use the current TCCL (application loader) > instead of resetting it to its own loader? > (ValidatorBuilder#getConfig: 116) > > Thank you in advance for your help, > Katya >
