Eric Johnson from the FuseSource documentation team, recently blogged about the fact, we from FuseSource, have plenty of professional documentation.
I can second Eric's observations. The level and quality of the documentation of the four Apache projects, can at best be used as a reference material.
As Eric says, FuseSource, have a professional team, who help writes documentation you cannot find at Apache, such as migration guides, performance tuning guides, deployment guides, transaction guides, management guides, and an operators handbook, etc. You may find pieces here and there scattered in the Apache documentation.
For example, when people ask me, what is Apache Camel, and how do they get started? Then I usually point them to an article - Open Source Integration with Apache Camel and How Fuse IDE Can Help written by Jonathan Anstey. This article introduces you to Camel, tells how its related to Enterprise Integration Patterns, shows a high level architecture overview, and talks about some of its concepts. And tie it all together with a sample use-case, with source code, that are explained.
Another good source is the chapter 1 (free) of the Camel in Action book. Jonathan is a co-author of this book, together with me.
There is of course also the FuseSource Mediation Router (Camel) introduction documentation as well.
![]()
![]()
![]()
![]()
![]()
![]()
Quoting Eric
I find it frustrating that so few people, people who use our products, realize the amount of documentation FuseSource offers on their products. I was talking to some users the other day who were shocked to discover that FuseSource offerers Javadoc for Fuse ESB. It rapidly becomes clear that people who complain about our documentation are usually complaining about the documentation they find at the Apache projects that make up the core of our offerings. I understand their frustration with the information on the Apache sites. It is often outdated, confusing, and hard to search. It is written by ninjas for other ninjas. The FuseSource Documentation team writes professional, versioned content targeted at more typical corporate IT professionals. We strive to make the content task oriented and relevant. We use better sample code, vet the content for accuracy, and organize it so that it can be searched effectively. Our documentation can be found at: It is available for free and, hopefully, is useful. We love to get feedback, so if you find issues or have ideas about how we can improve the content, leave feedback in the comment forms on the bottom of the pages. One of the writers will get back to you pretty quick.
I can second Eric's observations. The level and quality of the documentation of the four Apache projects, can at best be used as a reference material.
As Eric says, FuseSource, have a professional team, who help writes documentation you cannot find at Apache, such as migration guides, performance tuning guides, deployment guides, transaction guides, management guides, and an operators handbook, etc. You may find pieces here and there scattered in the Apache documentation.
For example, when people ask me, what is Apache Camel, and how do they get started? Then I usually point them to an article - Open Source Integration with Apache Camel and How Fuse IDE Can Help written by Jonathan Anstey. This article introduces you to Camel, tells how its related to Enterprise Integration Patterns, shows a high level architecture overview, and talks about some of its concepts. And tie it all together with a sample use-case, with source code, that are explained.
Another good source is the chapter 1 (free) of the Camel in Action book. Jonathan is a co-author of this book, together with me.
There is of course also the FuseSource Mediation Router (Camel) introduction documentation as well.
