[
https://issues.apache.org/jira/browse/CXF-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589669#action_12589669
]
Daniel Kulp commented on CXF-1530:
----------------------------------
For CXF's version of Aegis/Simple frontend, not having them on the wire is
probably correct. By default, we use minOccurs=0 for optional stuff so they
don't waste space on the wire and processing time parsing and stuff. Thus, if
XFire doesn't do the same thing, they may not be able to work together.
I would definitely agree with Benson to use the wsdl and generate jaxws+jaxb
clients for this.
> Nillable parameters not rendered.
> ---------------------------------
>
> Key: CXF-1530
> URL: https://issues.apache.org/jira/browse/CXF-1530
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.2, 2.0.4, 2.0.5
> Environment: Windows, Java 5, Service running on XFire, Client
> running CXF
> Reporter: Alexander Vaagan
>
> I have a service that accepts multiple arguments like this: MyResult
> getResults(ComplexInput arg0, AnOtherArgumentInput arg1).
> If I one or more of these arguments are null I get a fault from the service
> saying Not enough message parts. I have inspected the actual soap message
> sent over the wire and have confirmed that the parameters are not rendered.
> The service is running on XFire. (I am not able to migrate the service to CXF
> yet!)
> The problem exists on version 2.0.2, 2.0.4 and 2.0.5, but it seems to work on
> version 2.0.3.
> Both the service and the client uses AegisBinding. (Code first approach)
> /alex
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
