Hi Lucian, I've changed the error message in CVS [1] to the text I suggested. I suspect the reason the limit is in terms of nodes created is that it is easier to count than maxOccurs and has a small impact on performance when a security manager is registered. I'm just guessing though. The original author probably knows best.
Thanks. [1] http://cvs.apache.org/viewcvs.cgi/xml-xerces/java/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties?r1=1.76&r2=1.77&diff_format=h Lucian Holland <[EMAIL PROTECTED]> wrote on 06/10/2005 03:14:22 AM: > Michael, > > Many thanks for looking at this (apologies for the multiple emails > yesterday - not sure what was happening there!). It looks to my > uneducated eye like there was previously an attempt to shield users of > the SecurityManager from having to understand CMBuilder etc. by having a > magic MULTIPLICITY constant there to try and convert sum(maxOccurs) into > sum(ExpandedNodeCount); from the comment, it looks like this value was 3 > at some point. I'm assuming from the fact that this has now changed that > this was not particularly accurate and potentially misleading; if so, I > agree that the best thing would be to just change the error message to > reflect what really happens. In an ideal world it would be nice if one > could specify this in Schema terms - something like a "maximum particle > count", but I imagine that would get pretty complex for something that's > just an arbitrary security limit... > > Thanks again, > > Lucian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
