Hi Harald!
By default OWB takes the TCCL (ThreadContextClassLoader) into account. An EE
server (e.g. WAS or Geronimo) could swap the SingletonService before starting
up the container. But by default each WebApp will start it's own BeanManager
instance and it's own Extensions.
In our production app we e.g. have all the owb, myfaces, openjpa, bval, etc
jars in a shared ClassLoader. See the shared.loader setting in
${catalina.home}/conf/catalina.properties
Works superb!
LieGrue,
strub
----- Original Message -----
> From: Harald Wellmann <[email protected]>
> To: [email protected]
> Cc:
> Sent: Monday, June 25, 2012 3:37 PM
> Subject: Classloaders
>
> When creating multiple CDI containers from a single OpenWebBeans
> library working with multiple classloaders in parallel, how do you
> tell OpenWebBeans which classloader to use?
>
> Is there any alternative to setting the Thread Context Class Loader?
>
> Best regards,
> Harald
>
