View Replies (1)
Issue while Parsing XML Response after httpclient call
  1. New
  2. How-to
  3.  XML
0 Votes
  1. Nilanjan Chatterjee
  2. PowerBuilder
  3. Thursday, 18 September 2025 04:47 PM UTC

We are trying to migrate the SOAP calls to Httpclient as we would be migrating PB from 2017 to 2022.

Below is the XML response that we are getting when call using httpclient object

ls_response = '<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
        <types:MPSScreenBehaviourAgreementGetResponse>
            <MPSScreenBehaviourAgreementGetResult href="#id1" />
        </types:MPSScreenBehaviourAgreementGetResponse>
        <types:PassportWSResponse id="id1" xsi:type="types:PassportWSResponse">
            <responseObject href="#id2" />
        </types:PassportWSResponse>
        <types:BehaviourMsg id="id2" xsi:type="types:BehaviourMsg">
            <items href="#id3" />
        </types:BehaviourMsg>
        <soapenc:Array id="id3" soapenc:arrayType="types:BehaviourMsgItem[2]">
            <Item href="#id4" />
            <Item href="#id5" />
        </soapenc:Array>
        <types:BehaviourMsgItem id="id4" xsi:type="types:BehaviourMsgItem">
            <policyNumber xsi:type="xsd:int">2000101</policyNumber>
            <planId xsi:type="xsd:int">1</planId>
            <ppsgId xsi:type="xsd:int">0</ppsgId>
            <membershipId xsi:type="xsd:int">0</membershipId>
            <custId xsi:type="xsd:int">0</custId>
            <behaviourClass xsi:type="xsd:int">4</behaviourClass>
            <behaviourType xsi:type="xsd:int">2</behaviourType>
            <behaviourCode xsi:type="xsd:string">1</behaviourCode>
            <behaviourValue xsi:type="xsd:string">999999999</behaviourValue>
            <behaviourDisplayValue xsi:type="xsd:string" />
            <behaviourDescription xsi:type="xsd:string">Controls the number of funds allowed in the fund direction</behaviourDescription>
            <freezeSignal xsi:type="xsd:int">0</freezeSignal>
            <defaultValue xsi:type="xsd:boolean">true</defaultValue>
        </types:BehaviourMsgItem>
        <types:BehaviourMsgItem id="id5" xsi:type="types:BehaviourMsgItem">
            <policyNumber xsi:type="xsd:int">2000101</policyNumber>
            <planId xsi:type="xsd:int">1</planId>
            <ppsgId xsi:type="xsd:int">0</ppsgId>
            <membershipId xsi:type="xsd:int">0</membershipId>
            <custId xsi:type="xsd:int">0</custId>
            <behaviourClass xsi:type="xsd:int">4</behaviourClass>
            <behaviourType xsi:type="xsd:int">2</behaviourType>
            <behaviourCode xsi:type="xsd:string">3</behaviourCode>
            <behaviourValue xsi:type="xsd:string">DefaultBehaviour</behaviourValue>
            <behaviourDisplayValue xsi:type="xsd:string" />
            <behaviourDescription xsi:type="xsd:string">Identifies each group of policies whose member fund directions must be identical across said group of policies.</behaviourDescription>
            <freezeSignal xsi:type="xsd:int">0</freezeSignal>
            <defaultValue xsi:type="xsd:boolean">true</defaultValue>
        </types:BehaviourMsgItem>
    </soap:Body>
</soap:Envelope>'
 
We are trying to use PBDOM to parse and extract the value from the XML response (as we did not find any other option) through the below code but we are getting error.
 
TRY 
lpbdom_Doc = lpbdom_Builder.BuildFromString( lsResponse )            
ls_value = lpbdom_Doc.GetRootElement(). &
GetChildElement("Body", "soap","http://schemas.xmlsoap.org/soap/envelope/").&
  GetChildElement("BehaviourMsgItem","types","").gettext()
  GetChildElement("behaviourCode","","").gettext()          
CATCH (PBDOM_Exception lpbdom_Except) 
// Error Handling goes here, 
MessageBox( "PBDOM_Exception", lpbdom_Except.GetExceptionCode()) 
END TRY 
 
Please suggest if there is any other easier or better way by which we can parse the XML response and extract the values.
Catch-22 ? windows upgrade and offline license
Who is viewing this page
John Fauss
Nilanjan Chatterjee
Smruti Sahoo
Nageswararao Manchi
Responses (1)
  1. Likes
  2. Latest
  3. Oldest

Find Questions by Tag

.EXE .NET 6.0 .NET Assembly .NET Core 3.1 .NET Core Framework .NET DataStore .NET Std Framework 32-bit 64-bit ADO.NET AEM AI Algorithm Amazon AWS Android Apache API APK App Store App Store (Apple) Appeon Workspace Appeon Xcelerator Plug-in Architecture Array ASE Asynchronous Methods Authentication AutoBuild AutoCompiler Automated Testing Automation AutoScript Azure Barcode Base64 Batch BigData BLOB Branch & Merge Browser Bug Build Button C# C# Class Importer C# Editor C# Model generator Calendar Camera Certificate Chrome Citrix Class Client Client/Server Cloud Cluster Collection COM Command Line Compiler Compression Computed Field Configuration Controls Cookies Cordova Crash Cross-Platform Crosstab CSharpAssembly CSharpObject CSS CSV Cursor Data Database Database Driver Database Painter Database Profile Database Provider DataObject DataSource DataStore DataStore (C#) DataStore (PS) DataType DataWindow DATE DATETIME DB2 Debug Debugger Debugging Deployment Design DLL DO-WHILE Dockable Docker Documentation DOUBLE Download DPI DragDrop Edge Edit Style Editor Elevate Conference Email Embedded SQL Emulator Encoding Encryption Enhancement Request Entity Entity Framework ERP Error Event Event Handler Event Handling Excel Exception Export Expression External Functions F# Field File File Access Filter Firefox Firewall Font FOR-NEXT Foreground Format Function Garbage Collection GeoLocation Git Graph HANA Hash Header HTML/5 HTTP/S HTTPClient Icon IDE Identity IIS IMAPI Import InfoMaker Inheritance Installation Integer IntelliSense Interface Internet Internet Explorer iOS IPA iPad iPhone IWA J# Java JavaScript JBoss JDBC JOIN JSON JSONGenerator JSONParser Kestrel Label Lambda Large File LDAP Library License LINQ Linux OS Load Balancing Localization Localized PBVM Log In Log Out Logging LONG LONGLONG macOS MAPI Maps MDI Memory Memory Leak Menu Merge MessageBox Messagging Method Migration MIME TYPE Mobile Model ModelStore ModelStore (C#) MSOLEDBSQL Multi Threading MVC MySQL n-Tier Namespace NativePDF NVO OAuth ODATA ODBC Office Offline OLE OLEDB Online Open Source OpenAPI OpenSSL Oracle OrcaScript Other Outlook Output Package Parameter Patch PayPal PB Classic PB Native PB.NET PBC PBD PBDOM PBG PBJVM PBL PBNI PBORCA PBVM PBX PDF Performance Permission PFC Picture Pipeline Play Store (Google) Plugin Popup Port POST PostgreSQL PowerBuilder PowerBuilder (Appeon) PowerBuilder (SAP) PowerBuilder Compiler PowerBuilder Runtime PowerClient PowerScript (PS) PowerScript IDE PowerScript Migrator PowerServer PowerServer Mobile PowerServer Toolkit PowerServer Web PowerServerLabel Print Properties Proxy Publish PULL PUSH Query Regression Release Renew Resize Response REST Retrieve RibbonBar RibbonBar Builder RibbonView Rich Text Roadmap RPC Runtime Packager SaaS Scaffolding Script SDI SDK Security Server Service Session Single Sign-on Size SMTP SMTPClient SnapDevelop SOAP Solution Sort Source Code Speech Recognition SQL SQL Anywhere SQL Server SqlBuilder SqlExecutor SQLite SqlModelMapper Storage Stored Procedure Subscription SVN Swagger Syntax TabbedBar TabbedView Tablet TabPage Target TE Control Testing Text TFS Theme TIME Timer TLS/SSL Tomcat TortoiseGit TortoiseSVN Transaction Transparency Trial Trigger TRY-CATCH TX Control Type UI ULONG UltraLite Uninstall Unit Test Unit Testing UNIX OS Update Upgrade Upload URL User Center User Object UWP Validation VARCHAR Variable Versioning Visual Studio Visual Studio Code VM Voice Warning WCF Web API Web Extensions Web Service WebBrowser WebForms WebLogic WebSphere WildFly WinAPI Window Windows OS WinForms Wizard Workgroup Workspace WPF XCODE XHTML XML Zoom
✖

Helpful?

If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.