You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2007/09/28 14:53:59 UTC

[jira] Updated: (AXIS-1306) soapFault.setFaultString() etc do not create children...

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

Davanum Srinivas updated AXIS-1306:
-----------------------------------

    Assignee:     (was: Davanum Srinivas)

> soapFault.setFaultString() etc do not create children...
> --------------------------------------------------------
>
>                 Key: AXIS-1306
>                 URL: https://issues.apache.org/jira/browse/AXIS-1306
>             Project: Axis
>          Issue Type: Bug
>          Components: SAAJ
>    Affects Versions: current (nightly)
>            Reporter: Brian Ewins
>            Priority: Minor
>         Attachments: diff.txt
>
>
> If you create a fault using the saaj apis (MessageFactory.createMessage(),... etc) you'd expect that (saaj) SOAPFault.getChildElements() would get all the children of the fault, including the faultcode, faultstring and faultactor, once they have been set. In the Axis implementation, this is not the case - only SOAPFaultDetail objects can be returned.
> One way of fixing this (I guess) would be to create and retain a reference to the faultxxx SOAPElement after it has been set (in org.apache.axis.message.SOAPFault), but I can see there being issues with the element getting out of sync with the internal AxisFault.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org