You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/02 08:59:00 UTC

[jira] [Resolved] (CAMEL-8361) Camel Components - Generate per component XML schema

     [ https://issues.apache.org/jira/browse/CAMEL-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-8361.
--------------------------------
    Resolution: Won't Fix

> 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.x
>
>
> 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
(v8.20.10#820010)