Hi John, ServiceMix 4 (or ServiceMix Kernel 1.1) which is an OSGI platform integrating Apache Felix / Spring DM and PAX tools (like PAX URL, PAX Web, ...) is really a mature product and can be deployed in production.
This is not true what you say : ServiceMix 4 is fully compliant with JBI. You can check the documentation .Here is the link : http://cwiki.apache.org/SMX4KNL/does-servicemix-kernel-supports-jbi.html http://cwiki.apache.org/SMX4NMR/index.html And for a real example (which is not JBI/NMR based but use camel), have a look on my tutorial : http://www.dzone.com/links/how_to_design_a_soa_application_using_apache_came.html Regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com On Wed, May 6, 2009 at 3:51 PM, John <[email protected]> wrote: > Hi Charles, > > The primary reason is that we have Apache Http + Geronimo with a number of > applications already running in production. I wanted to take advantage of > JBI using ServiceMix so the easiest path, I thought, was to look at > integrating Geronimo and ServiceMix. > > To be perfectly honest, I haven't looked at SMX 4 or PAX Web and have only > a passing familiarity with Camel, though I like the DSL nature of it. > > Do you feel your suggestion is a viable platform for production use? The > one issue I have with SMX 4, right now, is that it isn't fully JBI compliant > yet, whereas 3.x is, so I was a little concerned about its maturity. > > Thank you for your response and I welcome any insight you might have on > this. > > John > > > Charles Moulliard wrote: > >> Hi John, >> >> I haven't made this integration so I can't answer to your question. >> >> For which reason, would you like to SMX 3.3 + Geronimo instead of by >> example >> using SMX 4 + Camel + PAX Web ? >> >> >
