Do some of those books handle the subject "best way to divide you ServiceMix ESB integration implementation into OSGi bundles"? Or some of non-book material? I haven't been able to find good material on this issue.
I have ordered (not received yet) a couple of those linked books, but they are general OSGi books, and I am hoping for more focus on ServiceMix/ESB/integration use case. This seems like a very fundamental issue when using ServiceMix. Everyone using ServiceMix needs to take some kind of approach to it. What are people usually doing? Someone must have written about it...any best practices or experiences? Filippo Balicchia wrote > Please see > http://karaf.apache.org/index/community/articles.html in book section > > Regards > > --Filippo > > > 2013/6/4 jmservicemix < > jannesm@ > > > >> Do you have any book suggestions? >> >> >> Johan Edstrom-2 wrote >> > This is a huge question and if you really want to succeed, grab a >> > few books and look at how systems are implemented. >> > >> > In general you want to promote small and modular systems >> > when writing OSGi code. If you are used to WAR/EAR deployments, start >> > re-thinking and re-using. >> > >> > /je >> > >> > On Jun 3, 2013, at 6:45 PM, Freeman Fang < >> >> > freeman.fang@ >> >> > > wrote: >> > >> >> Hi, >> >> >> >> Though you always need trade-off, put all things in one bundle isn't >> the >> >> good practice in OSGi world anyway. >> >> >> >> I'd say put each webserivce|camel router in different bundles should >> be >> >> the better way to go. >> >> －－－－－－－－－－－－－ >> >> Freeman(Yue) Fang >> >> >> >> Red Hat, Inc. >> >> FuseSource is now part of Red Hat >> >> Web: http://fusesource.com | http://www.redhat.com/ >> >> Twitter: freemanfang >> >> Blog: http://freemanfang.blogspot.com >> >> http://blog.sina.com.cn/u/1473905042 >> >> weibo: @Freeman小屋 >> >> >> >> www.camelone.org : The open source integration conference: >> >> >> >> On 2013-6-3, at 下午7:26, jimposervicemix wrote: >> >> >> >>> cross-posted at >> >>> >> http://stackoverflow.com/questions/16895593/advice-for-servicemix-bundle-design >> >>> >> >>> I am implementing an ESB solution using ServiceMix >> >>> >> >>> - I have my own system with a bunch of web services >> >>> - And several external systems with different services (most with WS >> >>> interfaces, some with others) >> >>> - These are to be connected with ServiceMix / Camel. Some message >> >>> routing, >> >>> transformation and other EIP is happening here. The solution is >> likely >> >>> utilizing JMS queues for between-bundles communication. >> >>> >> >>> Any advice on a good bundle design structure for this solution? >> Should >> I >> >>> just put everything in one bundle, should I have routing in one >> bundle >> >>> and >> >>> transformations for each external system in own bundle for each, >> >>> or....what >> >>> kind of structure would give enough benefits of modularity while not >> >>> being >> >>> overly complex to maintain? What should I take into account when >> making >> >>> the >> >>> decision? >> >>> >> >>> Any best practices or reference material for this kind of design >> >>> problem? >> >>> >> >>> I'm just looking for some general guidelines but I haven't found much >> >>> yet. >> >>> >> >>> >> >>> >> >>> -- >> >>> View this message in context: >> >>> >> http://servicemix.396122.n5.nabble.com/Advice-for-ServiceMix-bundle-design-tp5716937.html >> >>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://servicemix.396122.n5.nabble.com/Advice-for-ServiceMix-bundle-design-tp5716937p5716953.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> -- View this message in context: http://servicemix.396122.n5.nabble.com/Advice-for-ServiceMix-bundle-design-tp5716937p5716974.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
