Enterprise Integration Zone is brought to you in partnership with:

Ir. Charles Moulliard is a Sr. FuseSource Architect - Consultant and Apache Committer with more than 18 years of expertise in design of solution based on J2EE / .NET technologies. As a Solution Architect, he has been involved in system integration of client projects in Financial and Banking world. The skills (Methodology, UML, RUP, Project Management - Prince2, Telecommunication, Network, Security, Web Development, Programming languages, RDBMS, Architecture - J2EE/SOA, Middleware) that he acquires during its career path have help him to address business, functional, security and infrastructure requirements and transpose them into operable and efficient solutions. He is also fascinated to train people on new emerging technologies like SOA, OSGI, J2EE and ESB and provide consultancy for FUSE clients. As an Apache Committer he contributes since several years on the projects Apache Camel, Karaf and ServiceMix and uses these technologies as standards for integration projects. He is the author of the Camel Bindy DataFormat. Charles has posted 8 posts at DZone. You can read more from them at their website. View Full User Profile

3 Reasons to Use FuseSource Docs for Apache Camel, ServiceMix, and Karaf

05.01.2012
| 6321 views |
  • submit to reddit
As an Apache Committer but also FuseSource Consultant and Solution Architect, the documentation and its quality is a critical factor in my day by day work. Until now, even using google search engine, that was difficult to find in one place all the information required and a wasting time.

This situation has changed and I will give you three reasons to use/adopt FuseSource documentation for your Apache Camel, Apache ServiceMix and Apache Karaf projects.


Reason 1 :  Fuse maintains history of Apache releases

Apache websites uses Atlassian Confluence to maintain content publishes for each Apache project. This tool does not allow to create a history of the different releases of Camel by example (2.6, 2.7, 2.8). This is not the case with FuseSource documentation which allow you to browse a specific version like the current. And with the help of google, you can make specific search like that

    site:fusesource.com/docs/router/2.8/ "followed by the keywords"

or

    site:fusesource.com/docs/router "followed by the keywords"


Reason 2 : Javadoc and Schema are well documented


Javadoc like XML Schema are also 2 interesting examples as there is no XML Schema javadoc on Apache websites for by example Spring DSL language. This is completely different on FuseSource web site as you can read the documentation and discover what are the tags or attributes to be used for specific Apache Camel DSL words. Here is an example containing the options proposed for Apache Camel Dataformat.      http://fusesource.com/docs/router/2.8/xmlref/http.camel.apache.org.2033734988/element/dataformats.html




Reason 3 : New chapters have been added

FuseSource documentation contains missing pieces of information or cover in depth points which are described poorly on Apache websites or in an disparate way. So take the time to read the following chapters when you need more info about Transactions, Security, ...

Published at DZone with permission of its author, Charles Moulliard. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)