[
https://issues.apache.org/jira/browse/CAMEL-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350519#comment-14350519
]
Jim Northrup commented on CAMEL-8433:
-------------------------------------
for the benefit of any who need full namespace-enabled spring-beans documents
with camel-spring nested in spring:beans element I went ahead and tweaked the
2.14.1 xsd to close the gap on element/complextype relationships
https://github.com/jnorthrup/xcaml/blob/404e03dc08db2553b92d2e837cfdc061248f51a2/xacml-jaxp-model/src/main/xsd/camel-spring-2.14.1.xsd
this does not exhaustively inline all ComplexType declarations and in fact may
be overkill if "camelRoute" is the only such schema variation; but it allows
camel into the project that parses grammar #1 into grammar #2,#3,...n as jaxb
XSD proxies
> 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
> Assignee: Claus Ibsen
> 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)
