tag:blogger.com,1999:blog-2199838449876727292.post2330401248242597464..comments2024-03-12T00:49:57.094-07:00Comments on Henryk Konsek: Using Spring framework with Fabric8Henryk Konsekhttp://www.blogger.com/profile/09392743290349794069noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2199838449876727292.post-11961996352469950042014-07-27T01:54:11.213-07:002014-07-27T01:54:11.213-07:00Hi,
Actually I wrote this post to increase the aw...Hi,<br /><br />Actually I wrote this post to increase the awareness about the fact that Spring DM is not maintained anymore. And that Spring fan-boys should use for example the Fabric8's Spring Boot container instead.<br /><br />Regarding Blueprint - yes, it is supported in Fuse by all means. And it is definitely recommended for the OSGi deployments.<br /><br />The another thing is that it is worth to consider if you really want to follow the OSGi path. There are so many cool flat classpath alternatives in Fabric right now :) . This is my personal opinion, but flat classpath are so simple and easy to maintain. I <3 flat classpaths, I really do :) .<br /><br />Cheers. Henryk Konsekhttps://www.blogger.com/profile/09392743290349794069noreply@blogger.comtag:blogger.com,1999:blog-2199838449876727292.post-89146717758899911672014-07-24T10:14:00.578-07:002014-07-24T10:14:00.578-07:00Thanks for article. I haven't started prime ti...Thanks for article. I haven't started prime time with fabric8 yet, but plan to. Meanwhile, If writing bundle for Fuse OSGI container (or karaf) that uses Camel, i didn't realize use of Spring XML to express your Camel route was frowned upon. Oh well, there is always Blueprint. I suppose blueprint is still viable for new Camel development to be deployed to Fuse OSGI container?lcurryhttps://www.blogger.com/profile/01568142368502338154noreply@blogger.com