You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Guillaume Nodet <gn...@gmail.com> on 2006/10/09 16:17:15 UTC
Re: problem packaging multiple service unit dependant from the same component
Could you raise a JIRA please.
I thought it was fixed, but i guess i'm wrong.
You use the 3.0 release version, right ?
On 10/9/06, rspazzoli@imolinfo.it <rs...@imolinfo.it> wrote:
> I have a problem packaging multiple service unit dependant from the same
> component using the dependency way in pom. The same doesn't happen if I use the
> <property><componentName> way.
>
> If I package more than one (with only one is ok) serviceunit that use the same
> component in the same service assembly I receive the following error:
>
> [INFO] [jbi:generate-jbi-service-assembly-descriptor]
> [INFO] Generating jbi.xml
> [INFO] Determining component name for service unit su4
> [INFO] Determining component name for service unit su6
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] The service unit su6 does not have a dependency which is packaged as a
> jbi-component or a project property 'componentName'
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The service unit su6
> does not have a dependency which is packaged as a jbi-component or a project
> property 'componentName'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: The service unit su6
> does not have a dependency which is packaged as a jbi-component or a project
> property 'componentName'
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:271)
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:172)
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:116)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
>
>
> the error message is not true because the service unit does decleare a dependecy
> to a jbi-component. If I switch back to the property way so that I have one
> serviceunit using dependency and one or more useyng the property way it works.
>
> bye
> Raffaele
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same
comp
Posted by frankr <fr...@aqon.com>.
I'm having the same problem here. Is there a work aroung available?
gnodet wrote:
>
> Could you raise a JIRA please.
> I thought it was fixed, but i guess i'm wrong.
> You use the 3.0 release version, right ?
>
> On 10/9/06, rspazzoli@imolinfo.it <rs...@imolinfo.it> wrote:
>> I have a problem packaging multiple service unit dependant from the same
>> component using the dependency way in pom. The same doesn't happen if I
>> use the
>> <property><componentName> way.
>>
>> If I package more than one (with only one is ok) serviceunit that use the
>> same
>> component in the same service assembly I receive the following error:
>>
>> [INFO] [jbi:generate-jbi-service-assembly-descriptor]
>> [INFO] Generating jbi.xml
>> [INFO] Determining component name for service unit su4
>> [INFO] Determining component name for service unit su6
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] The service unit su6 does not have a dependency which is packaged
>> as a
>> jbi-component or a project property 'componentName'
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: The service unit
>> su6
>> does not have a dependency which is packaged as a jbi-component or a
>> project
>> property 'componentName'
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: The service
>> unit su6
>> does not have a dependency which is packaged as a jbi-component or a
>> project
>> property 'componentName'
>> at
>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:271)
>> at
>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:172)
>> at
>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:116)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
>> ... 16 more
>>
>>
>> the error message is not true because the service unit does decleare a
>> dependecy
>> to a jbi-component. If I switch back to the property way so that I have
>> one
>> serviceunit using dependency and one or more useyng the property way it
>> works.
>>
>> bye
>> Raffaele
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058.html#a6720320
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem packaging multiple service unit dependant from the same
component
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Hello Guillaume,
Thank you for your effort!
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a8047259
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem packaging multiple service unit dependant from the same component
Posted by Guillaume Nodet <gn...@gmail.com>.
This is now fixed in 3.1.
On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> Alas, that didn't help too.
> As workaround I've moved http endpoints to a single SU - that works. If you
> have another ideas, please let me know. I've added JIRA issue as well.
>
> Best regards, Maxim Tebenev.
> --
> View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7991188
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same
component
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Alas, that didn't help too.
As workaround I've moved http endpoints to a single SU - that works. If you
have another ideas, please let me know. I've added JIRA issue as well.
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7991188
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem packaging multiple service unit dependant from the same component
Posted by Guillaume Nodet <gn...@gmail.com>.
Not in the xbean.xml, but in the pom.xml, you should have
<plugin>
<groupId>org.apache.servicemix.tooling</groupId>
<artifactId>jbi-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<componentName>servicemix-jsr181</componentName>
</configuration>
</plugin>
Change the value to the component you use.
On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> I have xbean.xml describing http WS binding. It doesn't have <configuration>
> section (I used one from Bridge sample). Could you please point on sample
> xbean.xml with configuration tag or write simple snippet?
>
> Thanks!
> Best regards, Maxim Tebenev.
> --
> View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7990691
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same
component
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
I have xbean.xml describing http WS binding. It doesn't have <configuration>
section (I used one from Bridge sample). Could you please point on sample
xbean.xml with configuration tag or write simple snippet?
Thanks!
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7990691
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem packaging multiple service unit dependant from the same component
Posted by Guillaume Nodet <gn...@gmail.com>.
Could you please raise a JIRA ?
If you have a simple project that fails, please attach a zip to the
jira so that we can reproduce the problem.
The current workaround is to specify the <componentName>
parameter in the <configuration> section of the jbi plugin.
On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> Hi Guillaume,
>
> I've just built smx 3.1 from sources and still getting this error. Double
> checked that all 3.0 in pom files changed to 3.1. Do you have other ideas
> how to fix this issue what's the reason for that?
>
> May be that's a good practice to have dependency on a component from a
> single other component? - but that's too restrictive. I'm just novice in ESB
> in SMX.
>
> Thank you for your help.
> Best regards, Maxim Tebenev.
>
>
> --
> View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7990136
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same
component
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Hi Guillaume,
I've just built smx 3.1 from sources and still getting this error. Double
checked that all 3.0 in pom files changed to 3.1. Do you have other ideas
how to fix this issue what's the reason for that?
May be that's a good practice to have dependency on a component from a
single other component? - but that's too restrictive. I'm just novice in ESB
in SMX.
Thank you for your help.
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7990136
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem packaging multiple service unit dependant from the same component
Posted by Guillaume Nodet <gn...@gmail.com>.
You *should* be able to use the 3.1-SNAPSHOT maven plugin
without using the 3.1-SNAPSHOT ServiceMix container itself,
at least for packaging (this may lead to problems upon deployment,
not sure).
On 12/20/06, rspazzoli@imolinfo.it <rs...@imolinfo.it> wrote:
> I confirm I have the same problem with sm 3.0, alas never tried 3.1 snapshot.
>
> bye
> Raffaele
>
> Quoting Guillaume Nodet <gn...@gmail.com>:
>
> > Because the jbi maven plugin is released as part of servicemix,
> > and this is the one that cause such problems.
> > Could you try with 3.1-SNAPSHOT ?
> >
> > On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
> >>
> >> I'm using 3.0.
> >> I wonder how it may depend on smx version since that's build-time error.
> >>
> >> Best regards, Maxim Tebenev.
> >>
> >>
> >> gnodet wrote:
> >> >
> >> > Using 3.0 or 3.1-SNAPSHOT ?
> >> >
> >> > On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
> >> >>
> >> >> Hello guys,
> >> >>
> >> >> I'm constantly facing up with the same issues. Any thoughts on how it
> >> >> could
> >> >> be fixed?
> >> >> Thanks in advance.
> >> >>
> >> >> Best regards, Maxim Tebenev.
> >> >>
> >> >>
> >> >> Could you raise a JIRA please.
> >> >> I thought it was fixed, but i guess i'm wrong.
> >> >> You use the 3.0 release version, right ?
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >> http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7986498
> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7987589
> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
>
>
>
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the
same component
Posted by rs...@imolinfo.it.
I confirm I have the same problem with sm 3.0, alas never tried 3.1 snapshot.
bye
Raffaele
Quoting Guillaume Nodet <gn...@gmail.com>:
> Because the jbi maven plugin is released as part of servicemix,
> and this is the one that cause such problems.
> Could you try with 3.1-SNAPSHOT ?
>
> On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>>
>> I'm using 3.0.
>> I wonder how it may depend on smx version since that's build-time error.
>>
>> Best regards, Maxim Tebenev.
>>
>>
>> gnodet wrote:
>> >
>> > Using 3.0 or 3.1-SNAPSHOT ?
>> >
>> > On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>> >>
>> >> Hello guys,
>> >>
>> >> I'm constantly facing up with the same issues. Any thoughts on how it
>> >> could
>> >> be fixed?
>> >> Thanks in advance.
>> >>
>> >> Best regards, Maxim Tebenev.
>> >>
>> >>
>> >> Could you raise a JIRA please.
>> >> I thought it was fixed, but i guess i'm wrong.
>> >> You use the 3.0 release version, right ?
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7986498
>> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7987589
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same component
Posted by Guillaume Nodet <gn...@gmail.com>.
Because the jbi maven plugin is released as part of servicemix,
and this is the one that cause such problems.
Could you try with 3.1-SNAPSHOT ?
On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> I'm using 3.0.
> I wonder how it may depend on smx version since that's build-time error.
>
> Best regards, Maxim Tebenev.
>
>
> gnodet wrote:
> >
> > Using 3.0 or 3.1-SNAPSHOT ?
> >
> > On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
> >>
> >> Hello guys,
> >>
> >> I'm constantly facing up with the same issues. Any thoughts on how it
> >> could
> >> be fixed?
> >> Thanks in advance.
> >>
> >> Best regards, Maxim Tebenev.
> >>
> >>
> >> Could you raise a JIRA please.
> >> I thought it was fixed, but i guess i'm wrong.
> >> You use the 3.0 release version, right ?
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7986498
> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> >
>
> --
> View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7987589
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same
component
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
I'm using 3.0.
I wonder how it may depend on smx version since that's build-time error.
Best regards, Maxim Tebenev.
gnodet wrote:
>
> Using 3.0 or 3.1-SNAPSHOT ?
>
> On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>>
>> Hello guys,
>>
>> I'm constantly facing up with the same issues. Any thoughts on how it
>> could
>> be fixed?
>> Thanks in advance.
>>
>> Best regards, Maxim Tebenev.
>>
>>
>> Could you raise a JIRA please.
>> I thought it was fixed, but i guess i'm wrong.
>> You use the 3.0 release version, right ?
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7986498
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7987589
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem packaging multiple service unit dependant from the same component
Posted by Guillaume Nodet <gn...@gmail.com>.
Using 3.0 or 3.1-SNAPSHOT ?
On 12/20/06, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> Hello guys,
>
> I'm constantly facing up with the same issues. Any thoughts on how it could
> be fixed?
> Thanks in advance.
>
> Best regards, Maxim Tebenev.
>
>
> Could you raise a JIRA please.
> I thought it was fixed, but i guess i'm wrong.
> You use the 3.0 release version, right ?
>
>
>
> --
> View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7986498
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: problem packaging multiple service unit dependant from the same
component
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Hello guys,
I'm constantly facing up with the same issues. Any thoughts on how it could
be fixed?
Thanks in advance.
Best regards, Maxim Tebenev.
Could you raise a JIRA please.
I thought it was fixed, but i guess i'm wrong.
You use the 3.0 release version, right ?
--
View this message in context: http://www.nabble.com/problem-packaging-multiple-service-unit-dependant-from-the-same-component-tf2409058s12049.html#a7986498
Sent from the ServiceMix - User mailing list archive at Nabble.com.