Hi We got started on this 5 years ago. And my former client is retiring their last JCAPS integration this year.
Just being able to "free" your business logic and store this in a regular code repository like SubVersion, Git, etc is a big big win. And using regular Java / Spring code that everybody else has been doing for a decade is also a big win. And being able to use unit testing etc. And for great docs, then I suggest to read this intro article about Camel http://java.dzone.com/articles/open-source-integration-apache And if can afford to splash the cash, then you can consider the Camel in Action book (I am co-author of that book) As well there is other authors currently writing on new book(s) as well. So more books in the future about Camel. The docs on the Camel website, is not really well read as a book, but as a reference guide, as well for short articles about a specific topic. And use the search box on the front page to find links if you have some keywords. And then you can use this mailing list as the community is very active and often very responsive. Good luck. On Wed, Apr 24, 2013 at 8:28 AM, Fitzcaraldo <brian.fitzger...@marlo.com.au> wrote: > Hi > We're looking at a project to retire some JCAPS/ECANN interfaces for a > client and replace them with Camel routes. Has anyone done this before and > has tips or traps to share? > Thanks > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/JCAPS-to-Camel-tp5731389.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
