You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commons-dev@ws.apache.org by "Dobri Kitipov (JIRA)" <ji...@apache.org> on 2009/02/05 10:21:59 UTC

[jira] Updated: (WSCOMMONS-437) Define a common superinterface for SOAPFaultCode and SOAPFaultSubCode

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

Dobri Kitipov updated WSCOMMONS-437:
------------------------------------

    Attachment: SOAPFaultCode_patch.patch

Attach the SOAPFaultCode patch.

> Define a common superinterface for SOAPFaultCode and SOAPFaultSubCode
> ---------------------------------------------------------------------
>
>                 Key: WSCOMMONS-437
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-437
>             Project: WS-Commons
>          Issue Type: Improvement
>          Components: AXIOM
>            Reporter: Dobri Kitipov
>         Attachments: SOAPFaultClassifier.java, SOAPFaultCode_patch.patch, SOAPFaultSubCode_patch.patch
>
>
> Hi everybody,
> recently I have done some research on how SOAP Faults are generated. 
> If you look at both SOAPFaultCode and SOAPFaultSubCode it becomes obvious that SOAPFaultCode and SOAPFaultSubCode implementation can be refactored. My proposal is that both they can extend a common interface and thus make them more natural and reusable. No need of casting anymore.
> The fixes are applied to the current mail.
> Looking forward for your comments on this.
> thank you in advance,
> Dobri 

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