-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: 1 - Unexpected event, expected end-tag #45
Comments
Hello Oleg, The reason for the error is that erlsom expects one or more elements as The soap schema says: <xs:complexType name="detail"> So a valid error could look like this: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ Regards, On Fri, Aug 21, 2015 at 5:05 PM, Oleg notifications@github.com wrote:
|
Thanks for the reply. This is bad news, because i can't change a server side code. How can i say erlsom to accept the existent wrong format of detail element? |
You can change the schema, so that is an element of type string. On Fri, Aug 21, 2015 at 8:16 PM, Oleg notifications@github.com wrote:
|
If i'll replace here:
the line:
with:
Will erlsom parse both correct and incorrect result? |
That sounds like a good idea, give it a try. On Sat, Aug 22, 2015 at 9:31 AM, Oleg notifications@github.com wrote:
|
The results of my experiment: with:
i get:
with:
i get:
So, it seems i can't use any element in place of detail element or i do something wrong. |
You are right: if you just need to be able to parse the answer without What you might also try is to make the element of type "mixed" Good luck, On Sun, Aug 23, 2015 at 2:30 PM, Oleg notifications@github.com wrote:
|
So, with:
and with mixed="true" i get:
and with:
and without mixed="true" i get:
With mixed="true" the result looks more complicated, but it works! |
Hi.
Got the next error:
while processing the next soap xml response:
If i add the next line:
near 444 line of erlsom_parse.erl (before a throw call), i get the next output:
How can i eliminate this error?
Thanks.
The text was updated successfully, but these errors were encountered: