Question
Lantiqx
GB
Last activity: 29 Apr 2019 9:34 EDT
contains a simpleContent component in a mixed content type definition in SOAP Connector WIZARD
Hi,
While creating SOAP Connector via Wizard, in "Select Operations" Step, when clicked on Test button against one Operation, below error message is shown
Any pointer how to resolve this issue, will be much appreciated
Encountered issue in metadata:
com.pega.pegarules.pub.PRException: Schema for namespace '<NameSpace name>' contains a simpleContent component in a mixed content type definition
From: (unknown)
Thanks
Krishna
Accepted Solution
Lantiqx
GB
Thanks Kevin.
For others understanding, from URL above, copied and pasted below the exact Problem and solution
Problem: Mixed content
What to look for:
A complex element or type that uses the “mixed” attribute. Mixed content is used for mixing text with tagged element values. HTML is a common example of mixed content.
Thanks Kevin.
For others understanding, from URL above, copied and pasted below the exact Problem and solution
Problem: Mixed content
What to look for:
A complex element or type that uses the “mixed” attribute. Mixed content is used for mixing text with tagged element values. HTML is a common example of mixed content.
Example:
XSD Definition of MyElem1:
<!-- element with free-form markup content -->
<xs:element name=”MyElem1”>
<xs:complexType mixed="true">
<xs:sequence>
<xs:any minOccurs=”0” maxOccurs=”unbounded” processContents=”lax”/>
</xs:sequence>
</xs:complexType>
</xs:element>
Legal instances of MyElem1:
<MyElem1>This is an example of <b>mixed</b> content</MyElem1>
What it means:
Any text markup is allowed between the opening and closing tags for the element.
Why this is a problem:
First, see the example, above. In the example, it is unclear how data should be mapped to or from properties on a clipboard page. Additionally, when using elements with mixed content, you cannot treat the content the same way that you would treat regular text.
What to do:
First, replace the xs:complexType declaration with the xs:string type in the source XSD and use the accelerator to import it again. Then, to include HTML or markup in the XML, be sure to XML encode the tags embedded in the text. That way, the content can be treated as simple text.
Pegasystems Inc.
US
You may find this article helpful: https://community.pega.com/knowledgebase/articles/support-play-how-verify-and-troubleshoot-rules-created-xsd-or-wsdl#mixed
Accepted Solution
Lantiqx
GB
Thanks Kevin.
For others understanding, from URL above, copied and pasted below the exact Problem and solution
Problem: Mixed content
What to look for:
A complex element or type that uses the “mixed” attribute. Mixed content is used for mixing text with tagged element values. HTML is a common example of mixed content.
Thanks Kevin.
For others understanding, from URL above, copied and pasted below the exact Problem and solution
Problem: Mixed content
What to look for:
A complex element or type that uses the “mixed” attribute. Mixed content is used for mixing text with tagged element values. HTML is a common example of mixed content.
Example:
XSD Definition of MyElem1:
<!-- element with free-form markup content -->
<xs:element name=”MyElem1”>
<xs:complexType mixed="true">
<xs:sequence>
<xs:any minOccurs=”0” maxOccurs=”unbounded” processContents=”lax”/>
</xs:sequence>
</xs:complexType>
</xs:element>
Legal instances of MyElem1:
<MyElem1>This is an example of <b>mixed</b> content</MyElem1>
What it means:
Any text markup is allowed between the opening and closing tags for the element.
Why this is a problem:
First, see the example, above. In the example, it is unclear how data should be mapped to or from properties on a clipboard page. Additionally, when using elements with mixed content, you cannot treat the content the same way that you would treat regular text.
What to do:
First, replace the xs:complexType declaration with the xs:string type in the source XSD and use the accelerator to import it again. Then, to include HTML or markup in the XML, be sure to XML encode the tags embedded in the text. That way, the content can be treated as simple text.