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] Commented: (CXF-1277) JAXB schema validation fails for RPC
Date Mon, 10 Dec 2007 15:35:43 GMT

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

Daniel Kulp commented on CXF-1277:
----------------------------------


I'm not sure that is possible.   With RPC, it's VERY conceivable to to have multiple operations
with the same part name, but different types.   Example, the default for JAX-WS:

public Foo echoFoo(Foo f)
public Bar echoBar(Bar b)

whould result in BOTH operations having an unqualified "arg0" element, but the "type" for
one op would be foo and the "type" for the other would be Bar.   

To do this, we'd basically have to have internally created schemas for each Message object.
    That might work.   Not really sure though.


> 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
>
> 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