Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Bundlor issue with blueprint
Bundlor issue with blueprint [message #986450] Tue, 20 November 2012 13:15 Go to next message
Rigas Grigoropoulos is currently offline Rigas GrigoropoulosFriend
Messages: 9
Registered: November 2012
Junior Member
I am using Bundlor 1.1.2.RELEASE and trying to generate manifests for some blueprint projects.
Consider this simple test setup:
A project with only the following blueprint.xml file in resources/META-INF/ and no source or packages.
Note that the namespace links have been removed because unfortunately the forum does not allow to post links outside eclipse.org until I post 5 messages.
<blueprint xmlns="... blueprint namespace ..."
	xmlns:xsi="... XMLSchema namespace ..." 
	xmlns:context="... spring context namespace... "
	xsi:schemaLocation="... blueprint and spring context namespaces ..."
	default-activation="eager">

	<context:component-scan base-package="net.test.impl"/>
	<context:annotation-config />

	<bean id="entityManagerFactory"
		class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"/>
</blueprint>


Generating the manifest (either inside Eclipse or with a Maven build) creates this MANIFEST.MF:
Manifest-Version: 1.0
Tool: Bundlor 1.1.2.RELEASE
Import-Package: net.test.impl


which is missing the org.springframework.orm.jpa import.

Now changing only the first line of the blueprint.xml to the springframework namespace:
<blueprint xmlns="... springframework namespace ..."
	xmlns:xsi="... XMLSchema namespace ..." 
	xmlns:context="... spring context namespace... "
	xsi:schemaLocation="... blueprint and spring context namespaces ..."
	default-activation="eager">

	<context:component-scan base-package="net.test.impl"/>
	<context:annotation-config />

	<bean id="entityManagerFactory"
		class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"/>
</blueprint>


creates the correct manifest:
Manifest-Version: 1.0
Tool: Bundlor 1.1.2.RELEASE
Import-Package: net.test.impl,org.springframework.orm.jpa


The same happens with every tag in my blueprint files, only the package from the "context:component-scan" tag is picked up.
Is there any workaround to this?

[Updated on: Tue, 20 November 2012 13:17]

Report message to a moderator

Re: Bundlor issue with blueprint [message #996620 is a reply to message #986450] Wed, 02 January 2013 14:38 Go to previous message
Glyn Normington is currently offline Glyn NormingtonFriend
Messages: 1222
Registered: July 2009
Senior Member
It appears that bundlor does not support the blueprint namespace, although it does support the Spring framework namespaces. You could raise an enhancment bugzilla for bundlor. Meanwhile, specify the necessary package imports in your bundlor template file.
Previous Topic:Virgo 3.6.0 Released
Next Topic:Problem installing hibernate library bundles
Goto Forum:
  


Current Time: Wed Nov 26 23:27:13 GMT 2014

Powered by FUDForum. Page generated in 0.15126 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software