Export blueprint osgi bean and import it from other bundle
up vote
0
down vote
favorite
I trying to migrating from jboss fuse 6.x (spring-dm) to red hat fuse 7.x (blueprint). We are using spring-dm in fuse 6.x which no longer supported in fuse7.x.
In current project, we have create a common bundle which exposing the common function via the spring bean and it will be import by service bundles.
The spring xml in common bundle is place under META-INF/common/*.xml and expose via
<Export-Package>'=META-INF.common'</Export-Package>
The common bundle is use to configure the cxf buses, http conduit, common camel route and etc ...
The service bundles will then import these xml from bundle META-INF/spring/appContext.xml
<import resource="classpath*:META-INF/common/*.xml" />
As fuse 7.x only support blueprint and blueprint didn't support import resource.
We trying to embed the common bundle as library in each service bundle but this will need to rebuild all the service bundle if there are changes in the common bundle.
Is that anyway to achieve the same way that we did in spring-dm with blueprint?
apache-camel jbossfuse blueprint-osgi spring-dm
add a comment |
up vote
0
down vote
favorite
I trying to migrating from jboss fuse 6.x (spring-dm) to red hat fuse 7.x (blueprint). We are using spring-dm in fuse 6.x which no longer supported in fuse7.x.
In current project, we have create a common bundle which exposing the common function via the spring bean and it will be import by service bundles.
The spring xml in common bundle is place under META-INF/common/*.xml and expose via
<Export-Package>'=META-INF.common'</Export-Package>
The common bundle is use to configure the cxf buses, http conduit, common camel route and etc ...
The service bundles will then import these xml from bundle META-INF/spring/appContext.xml
<import resource="classpath*:META-INF/common/*.xml" />
As fuse 7.x only support blueprint and blueprint didn't support import resource.
We trying to embed the common bundle as library in each service bundle but this will need to rebuild all the service bundle if there are changes in the common bundle.
Is that anyway to achieve the same way that we did in spring-dm with blueprint?
apache-camel jbossfuse blueprint-osgi spring-dm
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I trying to migrating from jboss fuse 6.x (spring-dm) to red hat fuse 7.x (blueprint). We are using spring-dm in fuse 6.x which no longer supported in fuse7.x.
In current project, we have create a common bundle which exposing the common function via the spring bean and it will be import by service bundles.
The spring xml in common bundle is place under META-INF/common/*.xml and expose via
<Export-Package>'=META-INF.common'</Export-Package>
The common bundle is use to configure the cxf buses, http conduit, common camel route and etc ...
The service bundles will then import these xml from bundle META-INF/spring/appContext.xml
<import resource="classpath*:META-INF/common/*.xml" />
As fuse 7.x only support blueprint and blueprint didn't support import resource.
We trying to embed the common bundle as library in each service bundle but this will need to rebuild all the service bundle if there are changes in the common bundle.
Is that anyway to achieve the same way that we did in spring-dm with blueprint?
apache-camel jbossfuse blueprint-osgi spring-dm
I trying to migrating from jboss fuse 6.x (spring-dm) to red hat fuse 7.x (blueprint). We are using spring-dm in fuse 6.x which no longer supported in fuse7.x.
In current project, we have create a common bundle which exposing the common function via the spring bean and it will be import by service bundles.
The spring xml in common bundle is place under META-INF/common/*.xml and expose via
<Export-Package>'=META-INF.common'</Export-Package>
The common bundle is use to configure the cxf buses, http conduit, common camel route and etc ...
The service bundles will then import these xml from bundle META-INF/spring/appContext.xml
<import resource="classpath*:META-INF/common/*.xml" />
As fuse 7.x only support blueprint and blueprint didn't support import resource.
We trying to embed the common bundle as library in each service bundle but this will need to rebuild all the service bundle if there are changes in the common bundle.
Is that anyway to achieve the same way that we did in spring-dm with blueprint?
apache-camel jbossfuse blueprint-osgi spring-dm
apache-camel jbossfuse blueprint-osgi spring-dm
asked Nov 9 at 3:20
chiochuan
12
12
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53219378%2fexport-blueprint-osgi-bean-and-import-it-from-other-bundle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown