Rechecking the poms in servicemix, the servicemix-core
need to put put at provided scope, sorry.
On 9/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I did as you said, I created a dependency to servicemix-shared in my pom like
this:
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-shared</artifactId>
<version>3.0-incubating</version>
<scope>compile</scope>
</dependency>
this in turn provide servicemix-common and servicemix-soap. It does not provide
servicemix-core. So now the compilation fails because the class BaseLifeCycle
in servicemix-common depends from servicemix-core for resolvig the
MessageExchangeListener class.
thanks
Raffaele
----- Forwarded message from [EMAIL PROTECTED] -----
Date: Wed, 27 Sep 2006 16:56:05 +0200
From: Guillaume Nodet <[EMAIL PROTECTED]>
Reply-To: Guillaume Nodet <[EMAIL PROTECTED]>
Subject: Re: servicemix-common references servicemix-core
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
You just need to add a dependency to servicemix-shared.
You can remove the dependencies to servicemix-core and
servicemix-common as they will be brought in through
transitive deps.
The shared-library includes servicemix-core, you're right.
Unfortunately, petals lacks a lot of jbi standard features
that are required for servicemix-common based
components to work. I've tried some time ago
with petals M4 with no luck. Maybe it would work
now.
On 9/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> If I understand well it means that:
> 1. I should declare the dependency to servicemix-core ad provided
> 2. At runtime servicemix-shared must be deployed as shared library (in
> servicemix and any other ESB JBI).
> 3. Servicemix-shared contains servicemix-core.
>
> If the last (3) is correct I agree with you that more separation between
> components and container is needed. I don't know if I can help, but I
> intend to
> do some test with other container (petals) and I will surely let you know any
> relevant issues.
>
> thanks
> Raffaele
>
>
> Quoting Guillaume Nodet <[EMAIL PROTECTED]>
>
> > 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
>
>
>
>
>
--
Cheers,
Guillaume Nodet
----- End forwarded message -----
--
Cheers,
Guillaume Nodet
