Forum Discussion
Sharon
11 years agoNew Contributor
I have also run into this issue importing some third party WSDL/XSDs that previously imported fine. The instructions to add the line to vmOptions solves the issue, but it isn't very pretty. Could we instead get strict/not-strict import mode?
Note the schema in question does have an <?xml version="1.0" encoding="UTF-8"?> so I don't fully understand why it is suddenly failing.
Thanks,
Sharon
Note the schema in question does have an <?xml version="1.0" encoding="UTF-8"?> so I don't fully understand why it is suddenly failing.
Thanks,
Sharon
Related Content
- 8 years ago
- 4 years ago
- 10 years ago
- 9 years ago
Recent Discussions
- 22 days ago