[
https://issues.apache.org/jira/browse/CXF-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541654
]
Benson Margulies commented on CXF-1197:
---------------------------------------
Nothing ever calls JAXBDataBase.setSchema. That may be related.
> Schema wrong (?) for message part info in one JAXWS+JAXB case
> -------------------------------------------------------------
>
> Key: CXF-1197
> URL: https://issues.apache.org/jira/browse/CXF-1197
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.1
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
>
> If you de-ignore the DocLitWrappedTest in rt/javascript, you will see a
> failure. The error is a schema validation error, claiming that the schema for
> the MessagePartInfo for
> [MessagePartInfo name={uri:org.apache.cxf.javascript.fortest}parameters,
> ConcreteName={uri:org.apache.cxf.javascript.fortest}basicTypeFunctionReturnString
> calls for
> javax.xml.bind.UnmarshalException: unexpected element
> (uri:"uri:org.apache.cxf.javascript.fortest",
> local:"basicTypeFunctionReturnString"). Expected elements are <{}testBean1>
> testBean1 goes with something else entirely in this service's schema ... I
> haven't even gotten to trying to work with that.
> In other words, it looks like getSchema() is returning some else's schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
