[CAMEL-16607] RouteTemplateBeanDefinition : add suport for #type and #class languages

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.10.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Luca Burgazzoli
• Created: 12/May/21 08:47
• Updated: 14/May/21 05:46
• Resolved: 14/May/21 05:46

Description

The way to create a template with local beans in the YAML DSl is like:

- template: 
   id: "myTemplate"
   beans: 
     - name: "myProcessor"
       type: “#class|#type:com.acme.Product”
       properties:  
         - foo: "bar"

The bean is created by NamedBeanDefinition::newInstance

With the recent support for defining beans with a scripting language, we have some additional options and would be nice to merge the two ways in something like:

- template: 
   id: "myTemplate"
   beans: 
     - name: "myTypeBean"
       type: “#class|#type:...”
       properties:  
         - foo: "bar"
     - name: "myScriptedBean"
       type: “groovy|joor|...”
       script: “”

Issue Links

• relates to: CAMEL-16608 Kamelet local bean - Using script should allow to define return type of created bean
• links to: GitHub Pull Request #5559