Pega duplicates root element (urn) in WSDL

General
, ,
1

Hi guys! I have a question. I created SOAP service and parse XML rule thru the wizard in Pega 7.1.9.

But when I use deployed link and try to create requests to Pega to my service named putAcceptanceOffer it shows me two elements urn:putAcceptanceOffer

Maybe someone knows what should I check to fix this. Because of this duplicates it can’t be parsed but if I remove one of the tag it works. So why pega duplicate it? I think that first tag is service name, and the second tag is root element name in parse xml rule. But how I can configure service to include only one tag? Thanks in advance!

<soapenv:Envelope xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:urn=“urn:PegaRULES:SOAP:BVEBIntDBODeal:Services”>
soapenv:Header/
soapenv:Body
urn:putAcceptanceOffer
urn:putAcceptanceOffer

-------------My properties here-----------------

</urn:putAcceptanceOffer>
</urn:putAcceptanceOffer>
</soapenv:Body>
</soapenv:Envelope>

duplicate tags.png
duplicate tags.png1248×640 39.9 KB

2

@Artsiom_Sukhanau To resolve the issue of duplicate elements in your SOAP service, ensure that the root element node name in your XML Stream rule matches the expected root element node name in the external service. In your case, the root element in the XML Stream rule should be configured to match ‘putAcceptanceOffer’ as expected by the external service. This should prevent the duplication of the element and allow the request to be parsed correctly.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

org.xml.sax.SAXParseException; cvc-elt.1: Cannot find the declaration of element

3

@MarijeSchillern thanks for your reply! I don’t use external service. I use Service SOAP at pega side and final wsdl is generated using Parse XML rule on “Request” tab of the Service SOAP rule. I believe you saw attached screenshot and you can check that root element name in the Parse XML rule and parameter I use as a root element name in request parameters of service soap rule are the same. Maybe there is some option in Service Package rule which affects on this? But I’ve read all help articles about service packages and didn’t find anything helpful

4

@Artsiom_Sukhanau if the product is not working as documented then I would suggest that you formulate a reproducible workflow and log a support incident via the MSP so that our GCS team can investigate in depth.

→ Please provide the INC id here if you go down that route.

@ChrisKoyl @chars1 @PaulGentile_GCS can any of you help with this question?

5

@MarijeSchillern thanks for your answer! You know I tried the following:

  1. Create new Service Package

  2. Add my putAcceptanceOffer Service-SOAP in the new Service Package

  3. Deploy it

And it all works fine. It doesn’t duplicate any HTML headers or root elements or something other ghost elements… So I still think that the problem is on my old service package rule. But I can be wrong

All I know is “New methods duplicate its’ root element in old Service Package rules”