invalid XML attribute in OSLC of doorsNG
Hi,
from a oslc query like https://clmserver01....com/rm/views?oslc.query=true&projectURL=https%3A%2F%2Fclmserver01....com%2Frm%2Fprocess%2Fproject-areas%2F_tgOWwrPVEeGsn_ToVY7h1A&oslc.prefix=dcterms%3D%3Chttp%3A%2F%2Fpurl.org%2Fdc%2Fterms%2F%3E&oslc.select=dcterms%3Aidentifier%2C+dcterms%3Atitle%2C+dcterms%3Adescription%2C+*&oslc.where=dcterms%3Aidentifier%3E0&oslc.paging=true&oslc.pageSize=1000&page=2 I get an answer like this ... <oslc_rm:Requirement rdf:about="https://clmserver01....com/rm/resources/_m8y1KAuwEeKhdpYsFfQA9g"> <f1:accessControl rdf:resource="https://clmserver01....com/rm/accessControl/_tgOWwrPVEeGsn_ToVY7h1A"/> <nav:parent rdf:resource="https://clmserver01....com/rm/folders/_WLQp2wGlEeKx9oa7c1CPwg"/> <rt:_A7jPXCm8EeKTtIh3sdrW7g rdf:resource="https://clmserver01....com/rm/types/_7NbO6ym7EeKTtIh3sdrW7g#8d955ac0-b673-4472-8538-e9f822c9ebb8"/> <oslc:instanceShape rdf:resource="https://clmserver01....com/rm/types/_vC31S7PVEeGsn_ToVY7h1A"/> <rt:_KmRf0PwrEeGx9oa7c1CPwg rdf:resource="https://bt-clearquest....com/cqweb/restapi/CQ_BTQ_Prod/BTQ/RECORD/BTQ00154884?format=HTML&recordType=Request"/> <rt:_872G-xKuEeKYwrSFDI-vQw rdf:resource="https://clmserver01....com/rm/types/_eHJ2ywyEEeKhdpYsFfQA9g#439ee104-e218-4b61-88dc-76b5b6ec7161"/> ... which is fine most of times. But if the artifact has a link to an external URL, I get this portion <rt:_KmRf0PwrEeGx9oa7c1CPwg rdf:resource="https://bt-clearquest....com/cqweb/restapi/CQ_BTQ_Prod/BTQ/RECORD/BTQ00154884?format=HTML&recordType=Request"/> Where the & in the URL has not been encoded correctly (the "&recordType="), so my SAX parser is rightfully complaining about illegal XML. I am using Rational DOORS Next Generation 5.0.2 / RDNG5.0.2-I20141028_1800 / iFix005 maybe I'm missing something? Thanks for your help. Andreas |
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I can see similar issues. I suggest you open a ticket with Support to get it investigated further.
https://jazz.net/help/support/