[
https://issues.apache.org/jira/browse/CXF-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590239#action_12590239
]
Benson Margulies commented on CXF-1530:
---------------------------------------
What version did you make this patch against? We like to modify the trunk and
merge back, and I'm thinking you did this to 2.0.x since it doesn't apply to
the trunk cleanly.
Could you possibly pull a tree from svn and patch that? If not, I'll try to
work out how to apply your change to the trunk.
> 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
> Attachments: xmlstreamdatawriter.patch
>
>
> 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.
