[JAXP-14] Schema correctness check is too draconian Created: 16/Jan/07  Updated: 16/Jan/07

Status: Open
Project: jaxp
Component/s: www
Affects Version/s: current
Fix Version/s: milestone 1

Type: Improvement Priority: Major
Reporter: kohsuke Assignee: jaxp-issues
Resolution: Unresolved Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 14


See http://forums.java.net/jive/thread.jspa?threadID=21147&tstart=30

It would be really nice if the JAXP RI could report some of the schema
correctness problems as warnings (or in any other means that indicate those
errors are recoverable), as opposed to hard errors.

While this does seem like a correct error report, the fact of the matter is that
Microsoft is generating this kind of schemas in their WSDL (as well as other
parties — this error is fairly common), and we can't afford not to process those.

I do realize that this is a slippery slope, but please consider making this
change if possible.

Generated at Sat Nov 28 05:54:28 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.