[
https://issues.apache.org/jira/browse/CAMEL-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346385#comment-14346385
]
Jim Northrup commented on CAMEL-8433:
-------------------------------------
the project I am working on is generating route configs. since we are doing a
lot with other XSD's it is consistent to bring in the camel and spring xsd's to
provide a transform destination. perhaps a few annotations here and there
would help shore up the right element with the right class.
right now there is no xjc proxy for CamelContext, only the factories.
<camelContextFactoryBean> may or may not be legal camel config xml but it is
not documented that way.
> Camel XSD lacks Root Elements, does not generate round-trip Marshal/Unmarshal
> -----------------------------------------------------------------------------
>
> Key: CAMEL-8433
> URL: https://issues.apache.org/jira/browse/CAMEL-8433
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-javaconfig
> Affects Versions: 2.14.1
> Reporter: Jim Northrup
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> using xjc on the provided XSD file enclosing CamelContextFactory within a
> spring Beans XSD proxy creates an element "<CamelContextFactory>" instead of
> element "<camelContext>".
> additionally the Schema lacks root level element declarations and so the user
> of the generated beans is forced to hand-edit the generated output to insert
> @XmlRootElement("camelContext") in the camelContextFactoryBean generated bean.
> the solution is shown in github patch
> https://github.com/jnorthrup/xcaml/commit/531f042d8f8d5835a3030d6d8c1e6c3608c7b585?w=1
> along with other xjc descriptor amenities to successfully generate proxies
> that have elements sharing symbol names with attributes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
