[ 
https://issues.apache.org/jira/browse/CAMEL-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529684#comment-16529684
 ] 

Önder Sezgin commented on CAMEL-8361:
-------------------------------------

i did not look into this improvement area in deep but just had an idea to 
mentioned if my thinking would be worth thinking through around my idea.

so i think apt-compiler generates .json file per component, would it possible 
to convert them to their xml representation and generating an .xsd file per 
component using [trang.|http://www.thaiopensource.com/relaxng/trang.html] at 
this point not sure if the resulting xsd will be good enough to integrate with 
core model and have them work in all environments..

> Camel Components - Generate per component XML schema
> ----------------------------------------------------
>
>                 Key: CAMEL-8361
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8361
>             Project: Camel
>          Issue Type: New Feature
>          Components: tooling
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Now due to CAMEL-7999 we have information about each component and would be 
> able to create a maven plugin that generates per component XML schema, which 
> we can use in spring or blueprint to have per component type safe 
> configuration of both the component and endpoints.
> For example for endpoints something a like
> {code}
> <route>
> <from><file directory="somepath" recursive="true" include="*.txt"/></from>
> <to><jms queue="foo"/></to>
> </route>
> {code}
> Though there a few more tasks to this as we would need to
> - figure out how to integrate this with the camel model that is generated 
> from camel-core
> - how the namespace parsers of spring/blueprint detects these new namespaces 
> for each component
> - and have it work in all environments, eg standalone, jee, osgi, et all
> For starters we could allow to configure endpoints in the <endpoints> section 
> at first, an then later directly within the <routes>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to