This is not a bug. All components using servicemix-common depend on the servicemix-shared shared library which include all the needed classes to deploy the components in another JBI container if needed. However, they have not been really tested in other containers ... I'd like to have a cleaner separation between the components and container. If you want to help on that, you're welcome ...
On 9/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I'm developing a binding component and I'd like to depend only from servicemix-common which in turn should use only jbi compliant API, so that the component could be teorically installed on other ESB JBI. It looks like the class BaseLifeCycle in servicemix-common depends from servicemix-core for resolvig the MessageExchangeListener class. Is this correct or is this a bug? Thanks Raffaele
-- Cheers, Guillaume Nodet
