Forum Discussion

mmoser18's avatar
mmoser18
Frequent Contributor
8 years ago
Solved

Error opening soapUI project file from v5.3.0 with soapUI v5.2.1

We have a problem with the new soapUI version 5.3.0:   Some of our team have already upgraded to v5.3.0, others have not. Initially we had no issue with that but with our current version of our tes...
  • KarelHusa's avatar
    KarelHusa
    8 years ago

    I believe the only way to stay 100% compatible with 5.2.1 is to stay with 5.2.1 with all editors of the SoapUI project. The 5.3.0 version comes with changes and they are reflected in the project file XML structure.

     

    In your case, version 5.3.0 allows the status of access token having the value "UNKNOWN", whereas 5.2.1 did not.

     

    The set of allowed values is in 5.3.0:

     

     

        <xsd:simpleType name="AccessTokenStatus">
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="UNKNOWN"></xsd:enumeration>
            <xsd:enumeration value="ENTERED_MANUALLY"></xsd:enumeration>
            <xsd:enumeration value="WAITING_FOR_AUTHORIZATION"></xsd:enumeration>
            <xsd:enumeration value="RECEIVED_AUTHORIZATION_CODE"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVED_FROM_SERVER"></xsd:enumeration>
            <xsd:enumeration value="EXPIRED"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVAL_CANCELED"></xsd:enumeration>
        </xsd:restriction>
    </xsd:simpleType>

     

     

    In the version 5.2.1:

     

     

        <xsd:simpleType name="AccessTokenStatus">
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="ENTERED_MANUALLY"></xsd:enumeration>
            <xsd:enumeration value="WAITING_FOR_AUTHORIZATION"></xsd:enumeration>
            <xsd:enumeration value="RECEIVED_AUTHORIZATION_CODE"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVED_FROM_SERVER"></xsd:enumeration>
            <xsd:enumeration value="EXPIRED"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVAL_CANCELED"></xsd:enumeration>
        </xsd:restriction>
    </xsd:simpleType>

     

     

    If you want to convert the project file back to 5.2.1, I would try changing the value (UNKNOWN to e.g. EXPIRED) in the project XML and then to check in the 5.2.1 SoapUI. There might be other issues once you resolve this one.

     

KarelHusa's avatar
KarelHusa
Champion Level 3

I believe the only way to stay 100% compatible with 5.2.1 is to stay with 5.2.1 with all editors of the SoapUI project. The 5.3.0 version comes with changes and they are reflected in the project file XML structure.

 

In your case, version 5.3.0 allows the status of access token having the value "UNKNOWN", whereas 5.2.1 did not.

 

The set of allowed values is in 5.3.0:

 

 

    <xsd:simpleType name="AccessTokenStatus">
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="UNKNOWN"></xsd:enumeration>
            <xsd:enumeration value="ENTERED_MANUALLY"></xsd:enumeration>
            <xsd:enumeration value="WAITING_FOR_AUTHORIZATION"></xsd:enumeration>
            <xsd:enumeration value="RECEIVED_AUTHORIZATION_CODE"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVED_FROM_SERVER"></xsd:enumeration>
            <xsd:enumeration value="EXPIRED"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVAL_CANCELED"></xsd:enumeration>
        </xsd:restriction>
    </xsd:simpleType>

 

 

In the version 5.2.1:

 

 

    <xsd:simpleType name="AccessTokenStatus">
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="ENTERED_MANUALLY"></xsd:enumeration>
            <xsd:enumeration value="WAITING_FOR_AUTHORIZATION"></xsd:enumeration>
            <xsd:enumeration value="RECEIVED_AUTHORIZATION_CODE"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVED_FROM_SERVER"></xsd:enumeration>
            <xsd:enumeration value="EXPIRED"></xsd:enumeration>
            <xsd:enumeration value="RETRIEVAL_CANCELED"></xsd:enumeration>
        </xsd:restriction>
    </xsd:simpleType>

 

 

If you want to convert the project file back to 5.2.1, I would try changing the value (UNKNOWN to e.g. EXPIRED) in the project XML and then to check in the 5.2.1 SoapUI. There might be other issues once you resolve this one.

 

mmoser18's avatar
mmoser18
Frequent Contributor
8 years ago

From the instructions I wrote for myself and my colleagues:

 

If your soapUI v5.2.1 has issues opening the project file then either check out the latest version from soapUI or do the following:

 

  1. Open the file LHAPI-Tests-v5-soapui-project.xml in a text editor.
  2. Go to the very end of the file.
  3. Locate the line with the element "accessTokenStatus" (note: NOT accessTokenStartingStatus, just accessTokenStatus). It reads something like:
    <con:accessTokenStatus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">UNKNOWN</con:accessTokenStatus>
  4. Change that line to:
    <con:accessTokenStatus xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  5. Save the file and then restart soapUI. If it does not immediately reload the file, right-click on the entry and click "Reload". Now it should open the file… (hopefully).

 

Hope that helps!