Hi Team,
This is in continuation and reference to the thread https://developercenter.vmware.com/forums?id=4974#530183|3195755..
We now have a sample plugin (GlobalApp) from SDK samples along with the one that we develop. The solution suggested in the thread resolves the problem mentioned. But we see similar issue slightly different from the first one.
This seems to be a conflict on a class/service level and is coming out of spring/BlazeDS integration framework that connects the UI and the service framework.
To be specific, the concerned service interface is “org.springframework.flex.core.ExceptionTranslator”. Both GlobalApp and Cisco plugin provide an implementation for this with different service ids in the bundle-context.xml file as below...
Cisco :-
<osgi:service id="ExceptionService" ref="UcsExceptionTranslatorServiceImpl" interface="org.springframework.flex.core.ExceptionTranslator" />
GlobalApp :-
<osgi:service id="ExceptionTranslatorService" ref="ExceptionTranslatorServiceImpl" interface="org.springframework.flex.core.ExceptionTranslator" />
But somehow the class belonging to the plugin that is first deployed gets the preference and is the only one which is loaded.
We want to use our translator so that we can have our own custom exception. Please suggest a solution for the problem.
Regards
Manoj