axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-...@ws.apache.org
Subject [jira] Updated: (AXIS-1306) soapFault.setFaultString() etc do not create children...
Date Fri, 08 Oct 2004 11:46:51 GMT
The following issue has been updated:

    Updater: Ashutosh Shahi (mailto:ashutosh.shahi@gmail.com)
       Date: Fri, 8 Oct 2004 4:46 AM
    Comment:
Attaching a patch for the mentioned problem. Basically created faultcode, faultstring and
faultactor as child nodes of soapenv:Fault.Ran ant "all-tests", everthing seems to be working
fine.

Thanks,
Ashutosh
    Changes:
             Attachment changed to diff.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1306?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1306

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1306
    Summary: soapFault.setFaultString() etc do not create children...
       Type: Bug

     Status: Open
   Priority: Minor

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             current (nightly)

   Assignee: Davanum Srinivas
   Reporter: Brian Ewins

    Created: Tue, 13 Apr 2004 4:37 AM
    Updated: Fri, 8 Oct 2004 4:46 AM

Description:
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.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message