Hi,
Start from servicemix 3.3, we release maven-plugin separately, so the
jbi-maven-plugin version isn't same as the container
version,servicemix 3.3 use jbi-maven-plugin 4.0.
componentName property specify that which SE component or BC component
this SU belongs to, this is mandatory for generating SA descriptor.
In you case, you can aslo add servicemix-bean dependency in your su
pom.xml to avoid explictiy specifying the componentName property.
I guess somehow you already have servicemix-bean dependency in your su
pom so you needn't add componentName for servicemix 3.2.3
Freeman
On 2009-11-18, at 上午11:31, youhaodeyi wrote:
I am using servicemix 3.3. I can't find jbi-maven-plugin 3.3 so my
service
unit project pom.xml file uses jbi-maven-plugin 3.2.3. When I deploy
my
project, SMX will produce a warning that the service I deployed
doesn't have
componentName property. It works fine if I set the componentName to
"servicemix-bean" in my pom.xml file. When I change my project
dependents on
servicemix-3.2.3, it doesn't require such componentName property.
I wander what the componentName mean. Which jbi-maven-plugin version
do you
use?
thanks,
Zhao Yi
--
View this message in context:
http://old.nabble.com/Which-jbi-maven-plugin-will-be-used-for-servicemix-3.3--tp26401957p26401957.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
