Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Invalid XML WsDFUXRef response

Description

Several WsDFUXRef methods seem to return invalid XML responses.

For instance, DFUXRefMessagesQuery's sample response shows unstructured String response (based on WSDL):

DFUXRefMessagesQueryResponse>
<DFUXRefMessagesQueryResult>String</DFUXRefMessagesQueryResult>
</DFUXRefMessagesQueryResponse>

 

However, the response seems to include un-escaped XML data:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
<soap:Body>
<DFUXRefMessagesQueryResponse xmlns="urn:hpccsystems:ws:wsdfuxref">
<DFUXRefMessagesQueryResult>
<Messages>
<Cluster>mythor</Cluster>
</Messages>
</DFUXRefMessagesQueryResult>
</DFUXRefMessagesQueryResponse>
</soap:Body>
</soap:Envelope>

 

This causes WSDL generated code to fail.

This issue might be affecting these methods:

 

Conclusion

None

Activity

Show:

Kanghua Wang February 19, 2021 at 3:37 PM

  • Rodrigo
    i would think adding the inline exceptions to the wsdl would be very low impact right?

  • Rodrigo
    since the methods are returning exceptions inline already

Kanghua Wang February 17, 2021 at 4:39 PM

Does adding an option work for you?

Another choice is to add a version since we should not include un-escaped XML as a string. So, this is a bug fix. We may:

[depr_ver("1.01")] string DFUXRefMessagesQueryResult;

[min_ver("1.02")] string DFUXRefMessagesQueryResultNew;

But, the variable name has to be changed.

 

 

Rodrigo Pastrana February 17, 2021 at 4:20 PM

that should work. That would prob break current users, does it make sense to add an option to turn this on/off?

Kanghua Wang February 17, 2021 at 4:16 PM

Please see the screen capture in the attachment.

Rodrigo Pastrana February 17, 2021 at 3:52 PM

yes, perhaps. What do you have in mind?
<![CDATA[ <Messages>
<Cluster>mythor</Cluster>
</Messages> ]] >

or &lt;Messages&gt; &lt;Cluster&gt;mythor&lt;/Cluster&gt; &lt;/Messages&gt;

Either would likely work, but my concern is if it breaks anybody else.
How tough would it be to define the correct structure in ECM?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Major

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/14622

Roadmap

Not applicable

Created February 8, 2021 at 7:06 PM
Updated March 30, 2021 at 5:33 PM
Resolved March 30, 2021 at 5:33 PM

Flag notifications