You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2014/04/15 18:46:23 UTC

[jira] [Resolved] (CXF-5676) IllegalArgumentException: wrong number of arguments while invoking operation with only an implicit header parameter

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

Aki Yoshida resolved CXF-5676.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.0
                   2.7.12
                   2.6.15

I committed the fix including a slightly modified version of the test case provided by Andreas.



> IllegalArgumentException: wrong number of arguments while invoking operation with only an implicit header parameter
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-5676
>                 URL: https://issues.apache.org/jira/browse/CXF-5676
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 3.0.0-milestone2, 2.7.10
>            Reporter: Andreas Gudian
>            Assignee: Aki Yoshida
>             Fix For: 2.6.15, 2.7.12, 3.0.0
>
>         Attachments: implicit-header-with-no-args.zip
>
>
> I have an operation with no arguments, only an implicit header with direction {{IN}}. Calling the operation fails:
> {code}
> javax.xml.ws.soap.SOAPFaultException: wrong number of arguments while invoking public java.util.List sample.ImplicitHeaderWithExtSoapHeaderINSampleTest$ImplicitHeaderSampleImplementation.operationWithNoArgs(com.sample.audit.Audit) with params [com.sample.audit.Audit@c19fbf, com.sample.audit.Audit@c19fbf].
> 	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:159)
> {code}
> It works for operations with non-empty parameters and when the implicit header has direction INOUT.
> I'll attach a sample that demonstrates the issue.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.2#6252)