:(
Could you raise a JIRA and attach your project so we can find the problem ?

On 8/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I defined the parent pom as following:
     <parent>
         <groupId>org.apache.servicemix</groupId>
         <artifactId>samples</artifactId>
         <version>3.0-incubating-SNAPSHOT</version>
     </parent>

like wsdl-first example.
I have no other reference to servicemix versions, should I put one in
the plugin
declaration? Now my plugin declaration is:

       <plugin>
         <groupId>org.apache.servicemix.tooling</groupId>
         <artifactId>jbi-maven-plugin</artifactId>
         <extensions>true</extensions>
       </plugin>
thanks
Raffaele


Quoting Guillaume Nodet <[EMAIL PROTECTED]>:

> Which version do you use ? This bug has been fixed one month ago.
> See
>
http://svn.apache.org/viewvc/incubator/servicemix/trunk/tooling/jbi-maven-plugin/src/main/java/org/apache/servicemix/maven/plugin/jbi/GenerateServiceAssemblyDescriptorMojo.java?r1=418797&r2=426163&diff_format=h
> Make sure you use a recent version.
> Note that the version has been changed to 3.0-incubating-SNAPSHOT for
> consistency, so maybe you still
> reference the old ones ?
>
> On 8/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> As Grant noted I have the wanted order in the poms.
>> If in the su2's pom I declare a dependency to su1 is the plugin able to
>> undestand this kind of information?
>>
>> bye
>> Raffaele
>>
>> Quoting Grant McDonald <[EMAIL PROTECTED]>:
>>
>> > Just curious as to which POM/section would that be? He has the
ordering
>> set
>> > as 1,2,3,4 in the modules list as well as the sa dependencies and it
>> still
>> > produced 1,4,3,2
>> >
>> > -----Original Message-----
>> > From: Guillaume Nodet [mailto:[EMAIL PROTECTED]
>> > Sent: Tuesday, 29 August 2006 9:00 PM
>> > To: [email protected]
>> > Subject: Re: su declaration order in jbi.xml
>> >
>> >
>> > Well, this is not a bug, this is a feature of the maven plugin.
>> > The plugin makes sure that the order of the SU in the jbi
>> > descriptor is the same as in the pom.
>> > You need to order them in the pom :)
>> >
>> > On 8/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hi I have 4 su contained in one sa
>> >> su2 depends on su1
>> >> su4 depends on su3
>> >>
>> >> in the project with the pom packaging I have this configuration:
>> >>     <modules>
>> >>       <module>su1</module>
>> >>       <module>su2</module>
>> >>       <module>su3</module>
>> >>       <module>su4</module>
>> >>       <module>sa1</module>
>> >>     </modules>
>> >>
>> >> in sa1 pom I have this configuration:
>> >>
>> >>   <dependencies>
>> >>       <dependency>
>> >>         <groupId>it.imolinfo.iif.sample</groupId>
>> >>         <artifactId>su1</artifactId>
>> >>         <version>${pom.version}</version>
>> >>       </dependency>
>> >>       <dependency>
>> >>         <groupId>it.imolinfo.iif.sample</groupId>
>> >>         <artifactId>su2</artifactId>
>> >>         <version>${pom.version}</version>
>> >>       </dependency>
>> >>       <dependency>
>> >>         <groupId>it.imolinfo.iif.sample</groupId>
>> >>         <artifactId>su3</artifactId>
>> >>         <version>${pom.version}</version>
>> >>       </dependency>
>> >>       <dependency>
>> >>         <groupId>it.imolinfo.iif.sample</groupId>
>> >>         <artifactId>su4</artifactId>
>> >>         <version>${pom.version}</version>
>> >>       </dependency>
>> >>   </dependencies>
>> >>
>> >> so essentially I always declare the su in the order from 1 to 4.
>> >> When I use the maven plugin to create the service assembly the
>> > jbi.xmlgenerated
>> >> is the following:
>> >>
>> >>     <service-unit>
>> >>       <identification>
>> >>         <name>su1</name>
>> >>         <description>ServiceMix is an open source ESB based on the
Java
>> >> Business
>> >>     Integration framework - JSR-208</description>
>> >>       </identification>
>> >>       <target>
>> >>         <artifacts-zip>su1-0.0.1.zip</artifacts-zip>
>> >>         <component-name>iif</component-name>
>> >>       </target>
>> >>     </service-unit>
>> >>     <service-unit>
>> >>       <identification>
>> >>         <name>su4</name>
>> >>         <description>ServiceMix is an open source ESB based on the
Java
>> >> Business
>> >>     Integration framework - JSR-208</description>
>> >>       </identification>
>> >>       <target>
>> >>         <artifacts-zip>su4-0.0.1.zip</artifacts-zip>
>> >>         <component-name>servicemix-http</component-name>
>> >>       </target>
>> >>     </service-unit>
>> >>     <service-unit>
>> >>       <identification>
>> >>         <name>su3</name>
>> >>         <description>ServiceMix is an open source ESB based on the
Java
>> >> Business
>> >>     Integration framework - JSR-208</description>
>> >>       </identification>
>> >>       <target>
>> >>         <artifacts-zip>su3-0.0.1.zip</artifacts-zip>
>> >>         <component-name>iif</component-name>
>> >>       </target>
>> >>     </service-unit>
>> >>     <service-unit>
>> >>       <identification>
>> >>         <name>su2</name>
>> >>         <description>ServiceMix is an open source ESB based on the
Java
>> >> Business
>> >>     Integration framework - JSR-208</description>
>> >>       </identification>
>> >>       <target>
>> >>         <artifacts-zip>su2-0.0.1.zip</artifacts-zip>
>> >>         <component-name>servicemix-http</component-name>
>> >>       </target>
>> >>     </service-unit>
>> >>
>> >> so that the order is 1,4,3,2.
>> >>
>> >> when I deploy servicemix gets confused as it cannot resolve the
>> dependecy
>> >> from 4
>> >> on 3 and so the su4 is not initialized correctly.
>> >>
>> >> For dependecy between sus I mean that the dependant su expose the
>> endpoint
>> >> definied by the other su as a SOAP/HTTP webservice.
>> >>
>> >> If I manually reorder the jbi.xml to 1,2,3,4 all works well.
>> >> Any idea on whats causing the problem and how to resolve it?
>> >>
>> >> bye Raffaele
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>>
>>
>>
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet







--
Cheers,
Guillaume Nodet

Reply via email to