Incorrectly formatted XML in Rest API configuration page

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
9 years ago
5 months ago

People

(Reporter: briemers+bugzilla.mozilla.org, Assigned: gerv)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-1.fc11 Firefox/3.5.9 GTB7.0
Build Identifier: 0.6

The configuration xml contains the following:

<{START}>...</{START}>

However, the "{" character is not a part of a legal tag name.


Reproducible: Always

Steps to Reproduce:
1. query https://api-dev.bugzilla.mozilla.org/latest/bug/configuration?flags=0
2. Try parsing in any XML parser.
3.
Actual Results:  
<{START}> causes an unexpected character error.


Expected Results:  
I'm guessing {START} is supposed to be substituted on the  server side.

To work around this, I am doing a replaceAll before handing off the configuration to my XML parser.

Updated

9 years ago
Assignee: webservice → gerv
Component: WebService → BzAPI
Product: Bugzilla → Webtools
QA Contact: default-qa → bzapi
Version: unspecified → other
Again, the XML output is untested and unsupported.
https://wiki.mozilla.org/Bugzilla:REST_API#Data_Formats

That text is intentional; it's not supposed to be substituted. As you can imagine, serializing a data structure as XML is not a simple mapping - there are choices about how exactly you represent each value. Making the XML output supported would involve, among other things, going through sample XML outputs from each call and making sure only things that should be tag names were tag names, things that should be attributes were attributes, and things that should be nested tags were that.

Gerv
The XML output for the REST API is no longer supported in any way. It was always experimental, and I've decided to end the experiment. It's just too much hassle - sorry :-|

Gerv
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 3

9 years ago
Sounds like a good idea.   Really there is little use in having an output format that doesn't work quite right, with no resources to fix it.   If anyone needs it, I have APEX code to convert the JSON output into XML.

Updated

5 months ago
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.