SoapUI error loading wsdl - org.apache.xmlbeans.XmlException error: Unexpected element: CDATA

Error in SoapUI when creating a new SOAP Project

 When creating a new SOAP Project in SoapUI following error was given (as shown in the screenshot below) after providing the Project Name and URL of the wsdl. 
It was expected to get the service on the Left hand side pane along with the operations of the SOAP Web Services. However the error was about loading of the WSDL as the above screenshot shows.
So the WSDL url that was being provided was from the example below what you can see as below.

 So when creating a new SOAP Project in the SoapUI I was providing above URL which was as visible inside the Request screen shown in the above screenshot. 
The error message was "SoapUI error loading wsdl  - org.apache.xmlbeans.XmlException error: Unexpected element: CDATA". Stackoverflow and SoapUI blogs have several instances of this error message and none of the use case nor resolution steps worked. 
Here are few examples from Stackoverflow and SoapUI blogs with similar error message -
This pointed to a corrupt file 
This talks about perhaps Microsoft added elements or check the correct wsdl etc
This stackoverflow post is talking of a xsd schema tag
This stackoverflow post is talking about same error but after running a test
There are several such posts with the same error message but none of the solutions resolved the issue.
Now the resolution was simple. Turns out when creating a new SOAP Project, the URL to be given should not be as shown below. Even though this URL is visible in one of the Request screens as shown below with surrounded red line.

The correct WSDL url would be of the form ending with calculator.asmx?wsdl  (note the ?wsdl)
In short the above URL (shown in screenshot) is not correct as it is not the actual wsdl path. So when creating a new SOAP Project, always check the full path to a WSDL and use that to create the SOAP Project (typically ends with ?wsdl)
Resolution: After using the full path of WSDL the Project was successfully created and all the Service Operations were loaded and visible on the Left pane of SoapUI.

Comments

  1. Jake MathewsOctober 26, 2021 at 12:00 AM

    Thanks for sharing such a great post. It is very useful and informative. Valuable information you have shared. Also, check out
    <a href="https://www.akku.work/product/multi-factor-authentication.html>Multi-Factor Authentication</a>

    ReplyDelete
  2. UnknownApril 7, 2022 at 7:57 AM

    no me sirvio la info

    ReplyDelete
  3. EXPLORE COURSESJune 6, 2022 at 2:33 AM

    Hey, If you want learn about PMP then you must have read this - PMBOK® Guide: Top Differences Between PMBOK 7th vs 6th Edition!

    ReplyDelete

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Session Timeout in Oracle Access Manager

Image
Session Timeout in Oracle Access Manager (OAM) The session lifetime and Idle timeout entries control how long a user's session is valid. In OAM, a user session is an object which represents an authenticated user. This object is stored in the server memory and if Database session persistence is enabled, this object is stored or available in the database. Each session is unique and is identified by both a userid and Session ID (session identifier), see screenshot below "OAM User Session Management".  A valid session means a user has been authenticated with OAM. A session can have following three states: 1) active 2) inactive 3) expired When a session is created it is in active state and is available as an object in the OAM. After a set time - idle timeout, the session moves or transitions to inactive state. And finally after the Session Lifetime time, the session is marked as expired. Expired sessions are removed from server memory. Read more about Session Lifetime
Read more