[
https://issues.apache.org/jira/browse/CAMEL-20094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784989#comment-17784989
]
Karen Lease commented on CAMEL-20094:
-------------------------------------
The reason for this is that in camel-spring-xml there is a class
org.apache.camel.spring.xml.SpringErrorHandlerDefinition which contains the
following code
{code:java}
/**
* Error handler settings
*/
@Metadata(label = "spring,configuration,error")
@XmlRootElement(name = "errorHandler")
{code}
This conflicts with the core org.apache.camel.model.ErrorHandlerDefinition
{code:java}
/**
* Camel error handling.
*/
@Metadata(label = "configuration,error")
@XmlRootElement(name = "errorHandler")
{code}
Both generate an errorHandler.json file. The EipDocumentationEnricherMojo
plugin which adds the documentation to the generated schema files only uses one
of these files, apparently randomly, causing the description to change since
the javadoc is different.
Changing the javadoc will get rid of this issue but in fact, this conflict also
causes an incorrect schema since the errorHandler element
{code:java}
<xs:element name="errorHandler" nillable="true" type="xs:anyType">
{code}
does not reference the errorHandlerDefinition type even though it exists in the
schema.
It's not clear to me if the specific SpringErrorHandlerDefinition is actually
needed!
> camel-catalog: camel-spring.xsd keeps being regenerated
> -------------------------------------------------------
>
> Key: CAMEL-20094
> URL: https://issues.apache.org/jira/browse/CAMEL-20094
> Project: Camel
> Issue Type: Task
> Components: camel-catalog
> Affects Versions: 3.21.2, 4.1.0
> Reporter: Otavio Rodolfo Piske
> Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> There is something on the build that causes it to keep generating the
> camel-spring.xsd file. This is very annoying as it makes bisect automation
> harder, requires constant cleanups when rebasing and synchronizing branches.
> We should investigate why this is happening and fix it accordingly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
