Uploaded image for project: 'Content Gateway'
  1. Content Gateway
  2. CGW-332

Change in behavior has caused critical regression in jbosstools

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • None

      When executing a request to fetch fsw6.0 via download manager, at url https://www.jboss.org/download-manager/jdf/file/jboss-fsw-6.0.0.GA.zip

      I get the following xml response:

      <result>
          <workflow>
             <step>termsAndConditions</step>
             <tc>https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%3A%2F%2Fwww.jboss.org%2Fdownload-manager%2Ffile%2Fjboss-fsw-6.0.0.GA.zip&userName=rob.stryker&userType=J</tc>
             <tc-accept>https://developers.redhat.com/download-manager/rest/tc-accept</tc-accept>
          </workflow>
       </result>
      

      This response fails to be parsed by my parser, with the following exception:

      org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 226; The reference to entity "userName" must end with the ';' delimiter.
      	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
      	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:348)
      	at org.jboss.tools.foundation.core.xml.XMLMemento.createReadRoot(XMLMemento.java:88)
      	at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.findNextStep(DownloadManagerWorkflowUtility.java:96)
      

      I'm also a little why it's passing in a UserType, and would like some clarification on that point. It's possible that users can create similar requests and change the fields if they're l33t hax0rz, so it would be nice to know that parameter is absolutely required, or if it could just be figured out by the rest server.

            dhladky@redhat.com David Hladky
            rob.stryker Rob Stryker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: