[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jaxme-dev
Subject:    [jira] [Updated] (AXIOM-491) Migration struggles: it's too easy to add a SoapFault which is not of t
From:       "Andre Timmer (JIRA)" <jira () apache ! org>
Date:       2018-09-13 15:50:00
Message-ID: JIRA.13184940.1536853531000.68008.1536853800086 () Atlassian ! JIRA
[Download RAW message or body]


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

Andre Timmer updated AXIOM-491:
-------------------------------
    Description: 
Jar:  org/apache/ws/commons/axiom/axiom-impl/1.2.20/axiom-impl-1.2.20.jar

In org.apache.axiom.soap.impl.llom.SOAPBodyImpl and SOAPEnvelopeImpl it's too easy to \
add a Node that is a soap Fault but somehow not of type SOAPFault.

--  

Since Synapse 3.0.1 and the related axiom framework   a soap Fault   MUST be an \
instance of  SOAPFault. {color:#59afe1}Else the code doesn't recognise there is \
one!{color}

During our migration to Synapse 3.0.1 this resulted in some bugs that were hard to \
solve.

*Suggestion for  SOAPBodyImpl and  SOAPEnvelopeImpl*  

-  {color:#59afe1}add{color} to addChild method a {color:#59afe1}check{color} that \
when adding an element to the Body with name Fault this should be of instance \
SOAPFault  

  

  

  

  

  

  

  was:
Jar:  org/apache/ws/commons/axiom/axiom-impl/1.2.20/axiom-impl-1.2.20.jar

**In org.apache.axiom.soap.impl.llom.SOAPBodyImpl and SOAPEnvelopeImpl it's too easy \
to add a Node that is a soap Fault but somehow not of type SOAPFault.

  

  

  Since Synapse 3.0.1 and the axiom framework   a soap Fault   MUST be an instance of \
SOAPFault. Else the code doesn't recognise there is one!

During our migration to Synapse 3.0.1 this resulted in some bugs that were hard to \
solve.

Suggestion for  SOAPBodyImpl and  SOAPEnvelopeImpl  

-  add to addChild method a check that when adding an element to the Body with name \
Fault this should be of instance SOAPFault  

  

  

  

  

  

  


> Migration struggles: it's too easy to add a SoapFault which is not of the right \
>                 type
> ------------------------------------------------------------------------------------
>  
> Key: AXIOM-491
> URL: https://issues.apache.org/jira/browse/AXIOM-491
> Project: Axiom
> Issue Type: Bug
> Components: LLOM
> Affects Versions: 1.2.20
> Reporter: Andre Timmer
> Priority: Minor
> 
> Jar:  org/apache/ws/commons/axiom/axiom-impl/1.2.20/axiom-impl-1.2.20.jar
> In org.apache.axiom.soap.impl.llom.SOAPBodyImpl and SOAPEnvelopeImpl it's too easy \
>                 to add a Node that is a soap Fault but somehow not of type \
>                 SOAPFault.
> --  
> Since Synapse 3.0.1 and the related axiom framework   a soap Fault   MUST be an \
> instance of  SOAPFault. {color:#59afe1}Else the code doesn't recognise there is \
> one!{color} During our migration to Synapse 3.0.1 this resulted in some bugs that \
>                 were hard to solve.
> *Suggestion for  SOAPBodyImpl and  SOAPEnvelopeImpl*  
> -  {color:#59afe1}add{color} to addChild method a {color:#59afe1}check{color} that \
> when adding an element to the Body with name Fault this should be of instance \
> SOAPFault   
> 
> 
> 
> 
> 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


[prev in list] [next in list] [prev in thread] [next in thread]