You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "metatech (JIRA)" <ji...@apache.org> on 2011/07/07 14:10:16 UTC
[jira] [Commented] (SMXCOMP-791) NAME property in blueprint file
for servicemix-cxf-bc should keep same as the artifaceId for the the
component
[ https://issues.apache.org/jira/browse/SMXCOMP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061239#comment-13061239 ]
metatech commented on SMXCOMP-791:
----------------------------------
I had a similar error (see below).
I reinstalled ServiceMix and it worked again.
======
14:03:24,446 | INFO | rint Extender: 2 | Deployer | 124 - org.apache.servicemix.jbi.deployer - 1.4.0 | Deploying bundle 'null (wsdl-first-cxf-sa)' as a JBI service assembly
14:03:24,465 | WARN | rint Extender: 2 | Deployer | 124 - org.apache.servicemix.jbi.deployer - 1.4.0 | Requirements not met for JBI artifact in bundle null (wsdl-first-cxf-sa). Installation pending. org.apache.servicemix.jbi.deployer.impl.PendingException: Component not installed: servicemix-cxf-se
> NAME property in blueprint file for servicemix-cxf-bc should keep same as the artifaceId for the the component
> --------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-791
> URL: https://issues.apache.org/jira/browse/SMXCOMP-791
> Project: ServiceMix Components
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2010.02
>
>
> As the NAME property is used as componentName when deploy JBI component in OSGi container, also jbi-maven-plugin by default will use component artifactId as componentName from dependency when generated jbi descriptor for a certain SU, this mismatch will cause some error when install SA like
> Installation pending. org.apache.servicemix.jbi.deployer.impl.PendingException: Component not installed
> so we need change NAME property from servicemix-cxfbc to servicemix-cxf-bc
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira