You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by xm...@xml.apache.org on 2004/10/04 00:14:36 UTC
[jira] Updated: (XMLBEANS-65) support for Open Content Model
The following issue has been updated:
Updater: Aaron Anderson (mailto:aarona@augustmail.com)
Date: Sun, 3 Oct 2004 3:13 PM
Comment:
Please close this. Upon further examination I found the SchemaCompiler had the option NoUpa. I was using the ant task to build my xmlbeans which did not have the option to set it. I have attached a patch that adds it.
Changes:
Attachment changed to antask.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XMLBEANS-65?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XMLBEANS-65
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XMLBEANS-65
Summary: support for Open Content Model
Type: Improvement
Status: Unassigned
Priority: Major
Project: XMLBeans
Components:
Compiler
Versions:
Version 2
Assignee:
Reporter: Aaron Anderson
Created: Sat, 2 Oct 2004 3:40 PM
Updated: Sun, 3 Oct 2004 3:13 PM
Environment: Windows XP, xmlbeans-v2 from cvs
Description:
I am trying to run the schema compiler on the SPML 1.0 schema (http://www.oasis-open.org/committees/download.php/4138/os-pstc-spml-schema-1.0.xsd) and get multiple
[xmlbean] [ERROR] src/wsdl/os-pstc-spml-schema-1.0.xsd:85: error: cos-nonambig: Content model violates the unique particle attribution rule.
I believe they may be attributed to the fact that the SPML uses an "open content model" including multiple
<xsd:any minOccurs="0" maxOccurs="unbounded" processContents="lax" />
according to this post
http://lists.oasis-open.org/archives/provision-comment/200308/msg00001.html
Since the point of using the XMLBeans schema compiler is to generate typed java classes I am not sure how the "xsd:any" elements and attributes could be supported. Maybe an option to the schema compiler could be used to treat them as warnings instead of errors and skip over them.
I could modify the schema myself to remove them but I would rather use the original spec rather than maintaining two seperate versions of the spec
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org