Known issues

The following issues and limitations are known for Rhapsody® Model Manager 7.2 release.

Workaround

REST endpoint fails to parse RDF or XML when valid escaped entities (for example < or &) are unescaped before parsing

Internal ID: 83526

Problem: In ResourceRestService ( updateOSLCLinks ), all HTML/XML entities in the incoming RDF or XML request are escaped before passing it to Jena. This causes valid RDF or XML payloads from Doors Next (for example, artifact titles/descriptions containing < > represented as &lt; / &gt;, or attributes ) to be converted into invalid XML (< / > and &end=). The XML parser then throws SAXParseException.

Workaround: Removing the additional 'unescapeHtml' step allows the valid RDF or XML with escaped entities to parse successfully without affecting other flows including cases with UTF-8 (Ä).