[
https://issues.apache.org/jira/browse/CAMEL-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322665#comment-14322665
]
Claus Ibsen commented on CAMEL-8361:
------------------------------------
And we would need a new <components> that allow to configure components, like
we have for <dataformats>. Then ppl can do
{code}
<camelContext ...>
<components
<activemq id="foo" brokerUrl="tcp:..." maxReconnectAttempts="3"
prefetchSize="500" .../>
<jetty id="jetty" enabledJmx="true" maxThreads="100"/>
</components>
...
</camelContext>
{code}
Then inside components, its the components generated schema we use to configure
components. The id is likely optional so you can differentiate components or
given them a id. But if its omitted, then it should use the default component
name, eg jetty for jetty etc.
Now the component schema is maybe a mix of using attributes and elements. And
should also allow to use <property> style as well?
> 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
> 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
(v6.3.4#6332)
