Forum Discussion

aihnatsiuk's avatar
aihnatsiuk
Occasional Contributor
2 years ago

Failed to update the interface: [ Invalid QName value: Can't resolve prefix 'xs]

Hi, I get this error when trying to update the API definition in the existing project (we use Swagger):  Failed to update the interface: [ org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException...
Configuration
Function Tests
Integrations
REST
Server Monitoring
  • aihnatsiuk's avatar
    aihnatsiuk
    2 years ago

    srixon I figured out how to fix it. Not sure why but some of my API XML files started to contain this line

    "<con:type>xs:string</con:type>". I don't have it in the original definition. I successfully executed the update definition after removing "xs:" from ALL API calls 

richie's avatar
richie
Community Hero
Hi aihnatsiuk,

I have never seen a swagger/OAS define xml before, it's always been json, but the error youre getting seems pretty clear.

This isn't a ReadyAPI! issue.

It looks like you have an element or attribute definition in your swagger that is using an unknown namespace prefix of xs.

If you do a string search for 'xs:', interpreting the error response, it would appear you have an attribute or element with a namespace identifier that isnt recognised and remove the erroneous 'xs:' or change 'xs:' to the correct namespace identifier (depending on what you have defined)

Cheers,

Rich
srixon's avatar
srixon
Occasional Contributor
2 years ago

Hi richie

 

I encountered a similar error while attempting to update from a .yaml file.

 

Wed Jan 18 15:46:31 EST 2023: ERROR: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid QName value: Can't resolve prefix 'xs'
org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid QName value: Can't resolve prefix 'xs'

 

I searched the file for any instance of 'xs' and nothing turned up.

 

I'm not sure if anyone else solved this issue.  I'll keep digging in the meantime.

  • Skan28's avatar
    Skan28
    New Member
    5 months ago

    Is there any update here? I dont find such strings in the swagger.json file nor in my API .xml files. But i still get the error, where to look for it?