cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1277) JAXB schema validation fails for RPC
Date Mon, 02 Nov 2009 17:36:59 GMT

     [ https://issues.apache.org/jira/browse/CXF-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-1277.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.5


Managed to get JAXB to do this properly.   When writing, if you set the "declared type" for
the JAXBElement to Object.class, it writes out an xsi:type that the validator uses so the
element name is irrelevant.  When reading, I wrapper the XMLStreamReader with one that fakes
an xsi:type (if a type isn't on the wire) so, again, the validator can figure out what to
do.



> JAXB schema validation fails for RPC
> ------------------------------------
>
>                 Key: CXF-1277
>                 URL: https://issues.apache.org/jira/browse/CXF-1277
>             Project: CXF
>          Issue Type: Bug
>          Components: JAXB Databinding
>    Affects Versions: 2.1
>            Reporter: Benson Margulies
>            Assignee: Daniel Kulp
>             Fix For: 2.2.5
>
>
> If I turn on schema validation in CXF in an RPC server, it always fails. This is because
JAXB tries to validate the whole input message, and there's no schema in the wsdl for these
things. It seems to me that there could be schema: they are just form-unqualified elements
of the elements for the messages. Is there some reason-of-standardization why we can't just
include this in wsdl we generate? If so, we could fabricate it for runtime validation, I guess.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message