You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2008/02/21 19:57:19 UTC

[jira] Resolved: (CXF-964) CXF doesnt handle the Fault with primitive type (int) as fault detail.

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

Daniel Kulp resolved CXF-964.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.1)
                   2.0.4

> CXF doesnt handle the Fault with primitive type (int) as fault detail.
> ----------------------------------------------------------------------
>
>                 Key: CXF-964
>                 URL: https://issues.apache.org/jira/browse/CXF-964
>             Project: CXF
>          Issue Type: Bug
>          Components: Core, Tooling
>    Affects Versions: 2.0.1
>         Environment: windows
>            Reporter: Jeff Yu
>             Fix For: 2.0.4
>
>         Attachments: fault.wsdl
>
>
> Actually, there are two problems here:
> 1: with the wsdl, tool generate the @WebFault annotation with name "_int" instead of "int", it will cause the unmarshall problem, due to following code JaxwsServiceFactoryBean. (setFaultClassInfo method)
>         mpi.getConcreteName().getLocalPart().equals(name.getLocalPart() && name.getNamespaceURI().equals(ns))
> 2: After make changes to the @WebFault annotation, by changing the "_int" to "int", it can be unmarshalled successfully, but it will be looking for   (String, Integer) constructor, while the generated exception class only has the (String, int) class.
> Please test the attached wsdl with "ThrowIntFault" operation, and then you will see the problem as I described.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.