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 2021/06/22 08:46:00 UTC
[jira] [Commented] (CAMEL-16743)
https://camel.apache.org/schema/blueprint/camel-blueprint.xsd still has
headerName as required
[ https://issues.apache.org/jira/browse/CAMEL-16743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367145#comment-17367145 ]
Claus Ibsen commented on CAMEL-16743:
-------------------------------------
No its only removeHeader that mistakenly still have headerName as the attribute - but that is general in the core model
> https://camel.apache.org/schema/blueprint/camel-blueprint.xsd still has headerName as required
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-16743
> URL: https://issues.apache.org/jira/browse/CAMEL-16743
> Project: Camel
> Issue Type: Task
> Affects Versions: 3.10.0
> Reporter: Michael Oliver
> Priority: Minor
>
> The reference schema [https://camel.apache.org/schema/blueprint/camel-blueprint.xsd] still has headerName as required in setHeader element. But camel after version 3 has "name" vs. headerName in the setHeader element. Causing compile and build issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)