The validation you turn on is a schema validation. Catching exception regarding bad xml is something different. This said, please fill in a jira about this, we might evaluate removing the ignoreParseErrors=true flag.
We are getting the same issue. As of the jira, though the priority is major, no one is assigned. When it will addressed?
For the time being, what is the work around to proceed further
Scheduled for 3.2.1.
Though we are getting the same exception,. I have checked the response returned, the xml is valid. But could not found out why this exception occurs,.
AS you said, it is scheduled for 3.2.1, we have our deliverables by 15th. Is there any work around?
Excuse me, we are having this problem in out JBoss AS 4.2.3GA installation, I think that we can only run the 3.1.1 version of the JBoss WS Native libraries. What we can do in order to solve this problem?
Our problem happen when we try to access a WebService using the Birt Reporting Tool (WebService Data Source), the Birt is sending the following Request xml:
Thanks in advance