[
https://issues.apache.org/jira/browse/CXF-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-1464:
-----------------------------
Fix Version/s: 2.0.6
Just a note: I've got the wrapped fix working on the 2.0.x branch as well so
this will be included in 2.0.6.
To expand on the what Benson alluded to:
In wrapped mode, the uses cases should all be working as the operation name
gets serialized on the wire so we can figure out how to deserialize it on the
other side. All works well.
With bare mode, there are several problems:
1) All that ends up on the wire is something like <argo>Bug1</arg0>. There
isn't any information to help us determine if it's op2, op3, op5, or sayHi.
Thus, those cases probably won't work.
2) In the op4/op6 cases, there are two parameters. An xml document can only
have a single root. Thus, the XML binding will automatically flip those over
to a wrapped mode. The SOAP binding will not since they can both live under
the soap:body element. However, we then run into the <arg0> issue above.
Dan
> xmlbinding error
> ----------------
>
> Key: CXF-1464
> URL: https://issues.apache.org/jira/browse/CXF-1464
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.0.4, 2.1
> Environment: jdk1.5
> Fedora 8
> Reporter: Luca Ceppelli
> Assignee: Benson Margulies
> Fix For: 2.1, 2.0.6
>
> Attachments: ceppelli.cxf.bug.aegis.zip
>
>
> I'm trying to use CXF as backed for a web base application (Flex). Cxf has to
> expose json over http endpoint. The approach should be "code first" instead
> "wsdl first" for speeding up the development process.
> CXF has some problem with this (or maybe I was not able to run it properly),
> the problem is related with the xmlbinding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
