scomp problem with complextype and simplecontent

Hi, using scomp with the following schema part ... xsd:complexType name=typeMLSTRING00050 xsd:simpleContent xsd:restriction base=dtMLSTRING xsd:maxLength value=50/ xsd:minLength value=1/ /xsd:restriction /xsd:simpleContent /xsd:complexType ... I

Re: scomp problem with complextype and simplecontent

What's the type definition for dtMLSTRING? Sometime when you try to restrict a type which is in turn an extention of another type, you could run into problem with scomp. Thanks! Qian Holger Rieß

Re: scomp problem with complextype and simplecontent

Hi Qian, the definition of dtMLSTRING is xsd:complexType name=dtMLSTRING xsd:simpleContent xsd:extension base=dtSTRING xsd:attribute name=lang type=dtLANG use=optional/ /xsd:extension /xsd:simpleContent /xsd:complexType

Re: scomp problem with complextype and simplecontent

I think it's a scomp bug and we need to report this. I ran into this problem before, I was lucky enough to be able to change the schema so that I don't need to have extension and restriction running in the same line without losing much of my business logic. Don't know whether it's possible in

RE: Illegal characters, can xmlbeans be forgiving?

Have a look at the code in: $XMLBEANS/src/common/org/apache/xmlbeans/impl/common/EncodingMap.java and the code that calls it in $XMLBEANS/src/store/org/apache/xmlbeans/impl/store/Saver.java around line 1760 onwards EncodingMap.java contains all the supported encodings in the static

RE: scomp problem with complextype and simplecontent

Hi Holger Can you expand on this a bit? Is your complex type definition for typeMLSTRING00050 at the top level? Or put another way, what is surrounding your definition for typeMLSTRING00050? And what is at line 3681 of your schema bmecat_2005.xsd? It looks like something is using