[
https://issues.apache.org/jira/browse/CAMEL-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322666#comment-14322666
]
Claus Ibsen edited comment on CAMEL-8361 at 2/16/15 11:29 AM:
--------------------------------------------------------------
For component configuration we could start to allow using <property> style,
then we could allow to configure this without the schemas which are maybe not
yet ready.
<camelContext ...>
<components>
<component id="foo" name="activemq">
<property name="brokerUrl" value="tcp:..."/>
<property name="prefetchSize" value="{{someSize}}"/>
</component>
<component id="jetty">
<property name="enabledJmx" value="true"/>
<property name="maxThreads" value="100"/>
</components>
...
</camelContext>
was (Author: davsclaus):
For component configuration we could start to allow using <property> style,
then we could allow to configure this without the schemas which are maybe not
yet ready.
<camelContext ...>
<components
<component id="foo" name="activemq">
<property name="brokerUrl" value="tcp:..."/>
<property name="prefetchSize" value="{{someSize}}"/>
</component>
<component id="jetty">
<property name="enabledJmx" value="true"/>
<property name="maxThreads" value="100"/>
</components>
...
</camelContext>
> 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)
