[#PETALSBCSOAP-78] the exception thrown on PetalsESB is different than the exception of the original webservice. - Petals Link JIRA

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 4.0.5
Fix Version/s: 5.0.1
Component/s: None
Security Level: Public

Description:

Hide

Hi,
we are using PetalsESB with SOAP consumers and SOAP providers : Petals is a kind of layer between the REAL webservice, and the one invoked by our applications.
I use PetalsStudio to create the serviceunits and I deploy tham in the install folder of our ESB.
The problem is with exceptions : when calling the real webservice with an error in the SOAP packet ( invalid date for example) , we get this :

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <soap:Fault>
         <soap:Code>
            <soap:Value>soap:Sender</soap:Value>
         </soap:Code>
         <soap:Reason>
            <soap:Text xml:lang="en">Server was unable to read request. ---> There is an error in XML document (12, 47). ---> The string '2010-13-22' is not a valid AllXsd value.</soap:Text>
         </soap:Reason>
         <soap:Detail/>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

When passing thru the ESB, we get for the same error the following

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Client</faultcode>
         <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (9, 47). ---> System.FormatException: The string '2010-13-13' is not a valid AllXsd value. 
   at System.Xml.Schema.XsdDateTime..ctor(String text, XsdDateTimeFlags kinds) 
   at System.Xml.XmlConvert.ToDateTime(String s, XmlDateTimeSerializationMode dateTimeOption) 
   at System.Xml.Serialization.XmlCustomFormatter.ToDateTime(String value) 
   at System.Xml.Serialization.XmlSerializationReader.ToDateTime(String value) 
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read19_addabsence() 
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer32.Deserialize(XmlSerializationReader reader) 
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) 
   --- End of inner exception stack trace --- 
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) 
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) 
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() 
   --- End of inner exception stack trace --- 
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() 
   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
         <detail/>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

Why is this difference ? We have problems using the second answer in our java code , as it has been designed with the real webservice.

Is there an option I have to set in PetalsStudio ? I left all options as default..
Thanks

Show

Hi, we are using PetalsESB with SOAP consumers and SOAP providers : Petals is a kind of layer between the REAL webservice, and the one invoked by our applications. I use PetalsStudio to create the serviceunits and I deploy tham in the install folder of our ESB. The problem is with exceptions : when calling the real webservice with an error in the SOAP packet ( invalid date for example) , we get this :

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <soap:Fault>
         <soap:Code>
            <soap:Value>soap:Sender</soap:Value>
         </soap:Code>
         <soap:Reason>
            <soap:Text xml:lang="en">Server was unable to read request. ---> There is an error in XML document (12, 47). ---> The string '2010-13-22' is not a valid AllXsd value.</soap:Text>
         </soap:Reason>
         <soap:Detail/>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

When passing thru the ESB, we get for the same error the following

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Client</faultcode>
         <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (9, 47). ---> System.FormatException: The string '2010-13-13' is not a valid AllXsd value. 
   at System.Xml.Schema.XsdDateTime..ctor(String text, XsdDateTimeFlags kinds) 
   at System.Xml.XmlConvert.ToDateTime(String s, XmlDateTimeSerializationMode dateTimeOption) 
   at System.Xml.Serialization.XmlCustomFormatter.ToDateTime(String value) 
   at System.Xml.Serialization.XmlSerializationReader.ToDateTime(String value) 
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read19_addabsence() 
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer32.Deserialize(XmlSerializationReader reader) 
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) 
   --- End of inner exception stack trace --- 
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) 
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) 
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() 
   --- End of inner exception stack trace --- 
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() 
   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
         <detail/>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

Why is this difference ? We have problems using the second answer in our java code , as it has been designed with the real webservice. Is there an option I have to set in PetalsStudio ? I left all options as default.. Thanks

Environment:

Windows.

Issue Links

Depends

This issue depends on:
~~PETALSBCSOAP-164~~ SOAP Fault should be properly transformed to Fault or Error

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

2930d 16h 19m

1

Christophe DENEUX

Wed, 3 Apr 2019 - 08:25:44 +0200

Open

In Progress

4s

1

Christophe DENEUX

Wed, 3 Apr 2019 - 08:25:48 +0200

In Progress

Resolved

25s

1

Christophe DENEUX

Wed, 3 Apr 2019 - 08:26:13 +0200

Petals BC SOAP

the exception thrown on PetalsESB is different than the exception of the original webservice.

Details

Issue Links

Activity

People

Dates