About soapUI call error: error reading xmlstreamreader:
Record the process of solving each small bug without taking steps:
Problem Description:
Today is the first time to use WebService, and it is also the first time to call WebService. When calling with soapUI, an error is generated
Error reading xmlstreamreader: unexpected character
If it is deleted in the front, an error will be reported, and the text value behind it will be displayed
An error is reported after deleting the text values in all tags:
Error reading XMLStreamReader: Unexpected EOF in prolog
Through online inquiry, some people said it was a format error. After careful inspection, they found that there was no format error, and the verification was successful through the software itself
Solution:
Later, it was found that the back-end authentication was not released, so it was released. Finally, the problem was solved.
Similar Posts:
- The endpoint reference (EPR) for the operation not found possible problems and Solutions
- JQuery remote calling WebService reported an error, 500 error
- shell :syntax error: unexpected end of file
- [Solved] MYSQL ERROR 1093 – You can’t specify target table ‘readbook’ for update in FROM clause
- [Solved] kettle Error: Unexpected problem reading shared objects from XML file
- shell :syntax error: unexpected end of file
- [Solved] Javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
- IndentationError: unexpected indent python
- [Solved] VS error: 0xC0000005: Access violation/no source available when reading location 0xFFFFFFFFFFFFFFFF
- Problems of bad credentials, encoded password does not look like bcrypt in spring-cloud-oauth2 upgrade