Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
5 subscribers
Views
7125 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
I got this WstxUnexpectedCharException when trying to invoke a Web Service. Mor
rawich
over 9 years ago
I got this WstxUnexpectedCharException when trying to invoke a Web Service. More detail here:
An error occurred while invoking the operation {
schemas.microsoft.com/.../Services}Update
for the endpoint {
schemas.microsoft.com/.../Services}OrganizationService
and the service CustomBinding_IOrganizationService defined in the WSDL
appian.hostname.com:8080/.../63153
. An error occurred while invoking the Web Service. Details: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '"' (code 34) in DOCTYPE declaration; expected a space between public and system identifiers at [row,col {unknown-source}]: [1,50] (APNX-1-4044-000)
The same WSDL (attached here) and the service tested out fine in SoapUI.
This WSDL was edited to remove XSD constructs and other things not supported by Appian (Enumerations, WS-Policy, etc.). Instead of rehosting the WSDL on a web server, I stored the fi...
WSDL for Forum.wsdl
OriginalPostID-160555
OriginalPostID-160555
Discussion posts and replies are publicly visible
Parents
0
rawich
over 9 years ago
...le as a document in Appian, and created WebAPI that returns the WSDL as XML. So from Call Web Service node, this URL is used as WSDL:
appian.hostname.com:8080/.../63153
. If I put this into a browser window, I'll see the WSDL show up.
I tried googling and found a few threads discussed about this error from Axis2, but it doesn't seem to apply to this situation. Have anyone seen this before?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
rawich
over 9 years ago
...le as a document in Appian, and created WebAPI that returns the WSDL as XML. So from Call Web Service node, this URL is used as WSDL:
appian.hostname.com:8080/.../63153
. If I put this into a browser window, I'll see the WSDL show up.
I tried googling and found a few threads discussed about this error from Axis2, but it doesn't seem to apply to this situation. Have anyone seen this before?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data