You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2007/11/11 17:51:50 UTC
[jira] Created: (CXF-1197) Schema wrong (?) for message part info
in one JAXWS+JAXB case
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.
[jira] Commented: (CXF-1197) Schema wrong (?) for message part info
in one JAXWS+JAXB case
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-1197) Schema wrong (?) for message part info
in one JAXWS+JAXB case
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541655 ]
Benson Margulies commented on CXF-1197:
---------------------------------------
OK, this error isn't simply schema validation. UnmarshallingContext complains that 'the registry doesn't know about this element'.
So, maybe I've got wildly wrong XML here.
Since I'm working with a wrapped part, just what would I put into a DataWriter, I wonder, to get an examplar?
> 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.
[jira] Closed: (CXF-1197) Schema wrong (?) for message part info in
one JAXWS+JAXB case
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies closed CXF-1197.
---------------------------------
Resolution: Invalid
'There's nothing to see here, move along.'
> 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.