Not sure yet. What I had in mind was simply to use blueprint instead
of spring-dm for deploying components inside OSGi.
So I would replace
http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-file/trunk/src/main/resources/META-INF/spring/servicemix-file.xml
with a blueprint translation of it.
I hope that should be enough, but I might need to remove some
dependencies on spring interfaces (InitializingBean and such) if
needed to make sure they can run without spring if needed. I hope
that should be sufficient, but I'll post the result of my
investigation before committing anything.
Note that it should not have any impact on users.
Post by Charles MoulliardWhat is the impact to migrating SMX components from Karaf to Blueprint
? Could you elaborate a little bit please as I don't understand which
link exist today between SMX components and Karaf ?
KR,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel - ServiceMix Committer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard
Post by Lars HeinemannWhen reading the subject of the mail I was a bit confused ;)
But +1 from here as it will help solve some startup problems.
Regards
Lars
Post by Jean-Baptiste Onofré+1
Keep me posted if I can manage some components under your control.
Thanks
Regards
JB
Post by Guillaume NodetI'd like to migrate ServiceMix components to use Blueprint instead of
Karaf. This will remove some of the problems with startup time, where
some custom spring namespaces aren't available yet.
I'll start working on that today and I'll report back if there is any problem.
--
http://lhein.blogspot.com
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com