Forum Discussion

MikeLoundes's avatar
MikeLoundes
Contributor
11 years ago

[Resolved] Failed to update interface

Hi

I'm trying to update a wsdl def and keep getting the error message
'Failed to update interface:[com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException]'

error log has this in
com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.makeInvalidDefinitionException(WsdlLoader.java:140)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:127)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:565)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:545)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:565)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:545)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:236)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149)
at java.lang.Thread.run(Unknown Source)


Within the SoapUI log
Tue Jun 17 11:15:49 BST 2014:ERROR:Failed to load url [XXXXXXXXXXXXXXXXXXXXX]
Tue Jun 17 11:15:49 BST 2014:ERROR:An error occurred [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details
Tue Jun 17 11:15:50 BST 2014:ERROR:An error occurred [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details

I can take the url specified paste it into a browser and can see the xsd aok (note the xsd is a common one shared by other services that load aok into SoapUI, is there a limit on the path length??)


currently running soapui pro 4.6.4 on windows 8.1

the work around for me which is arduous is I take my current project xml file and send that onto somebody else who is running the non pro version 4.6.4 on win7
he imports the project updates the def saves and then sends back to me

I've tried disabling the proxy but it has no effect

please help
  • MikeLoundes's avatar
    MikeLoundes
    Contributor
    11 years ago
    OK sorted this now after lots of dead ends in searching for something related found this thread and the post from nov last year

    http://forum.soapui.org/viewtopic.php?f=4&t=22762#p52069

    has the this in it
    1) Open with a text editor the "soapUI-Pro-4.6.4.vmoptions" file located in the "bin" directory of the SoapUI Pro application
    2) Add this line at the end of the file:
    -Dfile.encoding=UTF8
    3) Save the file and restart SoapUI Pro
    Try again to load the WSDL in SoapUI Pro 4.6.4.

    the thread talks about default encoding used within SoapUI, checked on the guys box with the non pro version and he doesn't have that setting so I'm guessing that there's a difference between the two versions that unfortunately is an issue for pro users that isn't for non pro users
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    11 years ago
    Hi,

    As an FYI, there was a fix made in 4.6.4 maintenance (also included in 5.0 release) in which there was an issue with the original encoding not being persevered for the wsdl file. That is fixed in 5.0 and 4.6.4 maintenance. You can try downloading SoapUI Pro 5.0 and see if the problem is resolved. Since you do have a current workaround for 4.6.4 I will mark this thread as "resolved".


    http://www.soapui.org/Downloads/latest-release.html



    Regards,
    Marcus
    SmartBear Support
  • rlsmall's avatar
    rlsmall
    Visitor
    10 years ago

    In my Case I got this erro, but I forgot to check the WSDL URL as the project was imported from another user and they had their WSDL in a different location.

     

    So you might want to check your project properties.