[
https://issues.apache.org/jira/browse/XMLBEANS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cezar Andrei resolved XMLBEANS-237.
-----------------------------------
Resolution: Won't Fix
For loading we cannot throw an exception as a warning for a document that might
be the inteded one.
> Can we warn the user when they are running into the
> elementFormDefault="qualified" problem
> ------------------------------------------------------------------------------------------
>
> Key: XMLBEANS-237
> URL: https://issues.apache.org/jira/browse/XMLBEANS-237
> Project: XMLBeans
> Issue Type: New Feature
> Affects Versions: Version 2.1
> Environment: All
> Reporter: Lawrence Jones
> Priority: Minor
> Fix For: TBD
>
>
> It is common (and perfectly legal) for users to not include
> elementFormDefault="qualified" in their schemas and end up with the default
> value which is "unqualified". But often users don't realize the impact that
> this has on the requirements for namespace prefixes for local elements when
> interpreting the instance doc (a common mistake is to put xmlns="XXX" in a
> global element in the instance doc which then causes the local elements not
> to be picked up because under elementFormDefault="unqualified" they _must_
> have no namespace).
> Is it possible to warn them if we are seeing an instance doc that would fit
> the schema if elementFormDefault="qualified" was there? (Would need to
> consider what the perf impacts of this would be too).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
