|how to prevent double loading of blueprint extender (one loaded in kernel and one in user) [message #954880]
||Tue, 23 October 2012 10:19
| Yousef Fadila
Registered: October 2012
I face a lot of "class Cast exception" and type incompatible issues. when trying to inject blueprintcontainer and blueprintcontainer context caused, I assume, because of double loading to the blueprint extender interface in both kernel and user regions.
Some I solve by moving to reflection,(Inject to type object to bypass casting) but I want a solution for all. I can't change all jars to reflection.
for example now I have this problem when deploying the logger bundle.
[2012-10-23 19:33:09.424] INFO fs-watcher o.e.g.blueprint.extender.internal.activator.LifecycleManager Bundle logger is not type compatible with extender gemini-blueprint-extender; ignoring bundle...
Here is the bean created in its blueprint
<bean id="loggerManagerFactory" class="com.xxx.xxx.infra.core.logger.common.DefaultLoggerManagerFactory" >
<property name="loggerPrototypeId" value="logger-mgr-impl"/>
<property name="blueprintContainer" ref="blueprintContainer"/>
<bean id="logger-mgr-impl" class="com.xxx.xxx.infra.core.logger.log4j.manager.Log4jLoggerManager" scope="prototype">
<property name="bundleContext" ref="blueprintBundleContext"/>
any advice how can I solve this once for all jars?
[Updated on: Wed, 07 November 2012 09:56]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.03244 seconds