[
https://issues.apache.org/jira/browse/CXF-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933952#comment-15933952
]
Niels Bertram commented on CXF-7289:
------------------------------------
Yes the referenced issues all look alike. I have had a bit of a look at the
SchemaCompiler and the returned S2JJAXBModel after binding is complete and
there is nothing in there that cxf could use to identify "all" classes part of
this and other compilation episodes.
Bar any enhancements on the JAXB side, it might be possible to create a custom
XJC plugin that will simply inspect and store the XJC model during compilation
( {{com.sun.tools.xjc.Plugin#postProcessModel}} ).
Then we could pull out this plugin on
{{org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBDataBinding:L460}} with:
{code:java}
schemaCompiler.getOptions().getAllPlugins();
{code}
and extract the plugin and code model. Will need to check if we would be able
to get to the full code model inside the XJCPlugin.
Is that something the cxf team would be considering as a workaround?
> CXF wsdl2java fails when using existing compilation expisodes of schemata
> -------------------------------------------------------------------------
>
> Key: CXF-7289
> URL: https://issues.apache.org/jira/browse/CXF-7289
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 3.1.10
> Reporter: Niels Bertram
>
> Including a schema from an earlier compilation episode in a wsdl schema with
> the same namespace will cause to CXF fail when resolving the Java type when
> constructing the wsdl operation parameter.
> the issue is rather complex to demonstrate so I created a fully functioning
> compilation project at https://github.com/bertramn/cxf-wsdlgen-issue
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
