[CAMEL-12598] camel-tooling for code quality checks and anti-patterns

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Abandoned
• Fix Version/s: Future
• Component/s: tooling
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Claus Ibsen
• Created: 26/Jun/18 10:33
• Updated: 09/Jan/22 10:58
• Resolved: 09/Jan/22 10:58

Description

We have the camel-maven tooling that can do some scan of your project source code and report mis configured endpoints, and do route coverage reports etc.

It may be nice to gather a list of anti-patterns and other quality checks for Camel applications that can be commonly used. And then we can see if we can build more tooling to check for this.

Here is a few on top of my head (not thought for a long time)

 

• You could build a check for using deprecated options / components etc. DONE
   
• Also you can maybe check for too many <when> in a content based router EIP. (like too many if ... elseif ... in java)
   
• And maybe also if a route has too many EIPs (eg its too long).
   
• Also if a <recipientList> has a single endpoint, then its better to use <toD> which is optimized for a single endpoint. And also has some extra juice for http endpoints.