[Mono-bugs] [Bug 53667][Nor] New - MaxOccursString in ContentTypeParticle of XmlSchemaComplexType is not correct

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tcabanski@oai.cc.

http://bugzilla.ximian.com/show_bug.cgi?id=53667

--- shadow/53667	2004-01-31 09:28:28.000000000 -0500
+++ shadow/53667.tmp.31887	2004-01-31 09:28:28.000000000 -0500
@@ -0,0 +1,39 @@
+Bug#: 53667
+Product: Mono/Class Libraries
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.XML
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: tcabanski@oai.cc               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: MaxOccursString in ContentTypeParticle of XmlSchemaComplexType is not correct
+
+Well, back to the nasty JDF schema.
+
+I have a JMF element, which is of type JmfRootMessage.  This type is an 
+extension of BaseElement.  The ContentTypeParticle of the complex type 
+has the following values
+
+MaxOccursString = really big number
+MaxOccurs = <decimal value bigger than Int.MaxValue; same as above>
+MinOccursString = 0
+MaxOccurs = 0
+
+Microsoft gives:
+
+MaxOccursString = unbounded
+MaxOccurs = <decimal value bigger than Int.MaxValue>
+MinOccursString = 0
+MinOccurs = 0
+
+I believe the MaxOccursString should be unbounded.  I can work around 
+this problem by treating max occurs of this size to be unbounded in my 
+Mono version.