I am not sure if this will help you, but please try modifying your
maven-bundle-plugin configuration. The configuration below should be a
little more accommodating.
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
<configuration>
<instructions>
<Bundle-Name>${project.name}</Bundle-Name>
<Bundle-SymbolicName>${pom.groupId}.${pom.artifactId}</Bundle-SymbolicName>
<Import-Package>
!com.intrinsec.esb.components.vmware.vsphere.*,
*;resolution:=optional
</Import-Package>
<DynamicImport-Package>*</DynamicImport-Package>
<Embed-Dependency>*;scope=(compile|runtime)<Embed-Dependency>
<Export-Package>
com.intrinsec.esb.components.vmware.vsphere.*;version=${project.version},
META-INF.services.org.apache.xbean.spring.http.esb.intrinsec.com/components/vmware/vsphere-bc
</Export-Package>
<_removeheaders>Ignore-Package,Include-Resource,Private-Package</_removeheaders>
<Export-Service>
javax.jbi.component.Component;NAME=vsphere-bc;TYPE=service-engine,
org.apache.aries.blueprint.NamespaceHandler;osgi.service.blueprint.namespace="
http://esb.intrinsec.com/components/vmware/vsphere-bc/${project.version}";
</Export-Service>
</instructions>
<unpackBundle>true</unpackBundle>
</configuration>
</plugin>
Thanks,
SMS Chauhan
On Tue, Nov 9, 2010 at 11:39 PM, Emmanuel Guiton <
[email protected]> wrote:
> Hello All,
>
> After having successfully developed and tested a custom binding component,
> I am now trying to use a simple XML configuration file instead of the
> original SU and SA.
> I am stuck on the following error each time I copy the XML file (cf
> attached file) in the hot deploy directory :
> First, "Exception in thread "SpringOsgiExtenderThread-46"
> java.lang.IllegalStateException: BeanFactory not initialized or already
> closed - call 'refresh' before accessing beans via the ApplicationContext"
> appears in the console.
> Displaying logs, I notice
> "org.springframework.beans.factory.BeanDefinitionStoreException:
> Unrecognized xbean namespace mapping:
> http://esb.intrinsec.com/components/vmware/vsphere-bc/1.0";
>
> Listing the corresponding OSGI service, I can see the namespace :
> vSphere Binding Component (629) provides:
>
> ----------------------------------------------------------------------------
> osgi.service.blueprint.namespace =
> http://esb.intrinsec.com/components/vmware/vsphere-bc/1.0
> objectClass = org.apache.aries.blueprint.NamespaceHandler
> service.id = 444
>
> I did not notice any difference between my custom binding component
> (attached pom and blueprint files) and the servicemix-http component, except
> for the namespace being declared in the Export-Service section of the
> Manifest file in servicemix-http (I do not have this section in the Manifest
> file of the custom component). Could it be really linked to the issue ?
>
> Any hint would be greatly appreciated.
>
> Regards,
> - emmanuel
>
> --
> Ingénieur études et développements
> Intrinsec
> 215, avenue Georges Clemenceau
> 92000 Nanterre
> http://www.intrinsec.com
>
>
>
>
>
> Emmanuel GUITON
>
> Ingénieur développement Standard : +33 1 41 91 77 77 l Fax : +33 1 41 91 77
> 78
>
> 215, avenue Georges Clemenceau l 92024 NANTERRE
>
> http://infogerance.intrinsec.com/2010/04/informatique-de-lunicef-un-cloud-au-secours-dhaiti.html
> http://www.intrinsec.com/
>
>
>
