Hi Gareth, I am sorry, I did not try out the described workaround yet, because I didn't understand it in detail. Further, I was working on a different project for the last weeks, so that I didn't reply.
My question concering the workaround: does the described workaround mean, that I have to parse my XML file first manually (not with Xerces) and re-format it, so that each "line" ending with a semicolon is written into a single node? Thanks for your reply, Michael > > > Hi, > there was a return mail with a description of a possible > workaround. I assumed that since you did not reply, this > helped you. Was > that not the case? > > Gareth > > > On Thu, 3 Jun 2004, Heeg, Michael wrote: > > > Hi once again, > > > > I still have the problem with patterns as described below. > Is this an > > "official bug" of Xerces 2.5.0 now? Has anyone developed a > solution for > > this problem? > > > > Best regards, > > Michael > > > > > Betreff: Strange problem with pattern (Xerces 2.5.0 crashes) > > > > > > > > > Hi, > > > > > > I am using Xerces-C 2.5.0 in my MS Visual C++ application. > > > When validating > > > XML files against a specified schema, the parser sometimes > > > crashes with an > > > "unexpected exception". I found out that the reason for the > > > crashes is the > > > following restriction of the schema (see "Body" element): > > > > > > <xsd:complexType name="InputFileType"> > > > <xsd:sequence> > > > <xsd:element name="Head" type="HeadType"/> > > > <xsd:element name="Body"> > > > <xsd:simpleType> > > > <xsd:restriction base="xsd:string"> > > > <xsd:pattern > > > value="(\n*[0-9]*,[0-9]*,(\-*[0-9]*\.*[0-9]*,)*\-*[0-9]+\.*[0- > > > 9]*;\n*)*"/> > > > </xsd:restriction> > > > </xsd:simpleType> > > > </xsd:element> > > > </xsd:sequence> > > > </xsd:complexType> > > > > > > The restriction is defined to validate <Body> tags like > the following: > > > > > > <Body> > > > 0,10,0.199,10.199,0.008; > > > 1,20,0.389,20.389,0.059; > > > 2,30,0.565,30.565,0.180; > > > 3,40,0.717,40.717,0.369; > > > 4,50,0.841,50.841,0.596; > > > 5,60,0.932,60.932,0.810; > > > .... > > > </Body> > > > > > > The strange thing is: when the <Body> tag contains a large > > > amount of data, > > > the validation of the restriction leads to the unexpected > > > exception. But: > > > with a small amount of data, everything works fine. (Also: > > > when I delete the > > > restriction from the schema, everything works fine.) > > > > > > For me this looks like a Xerces bug?! Am I wrong? Any > suggestions or > > > comments? > > > > > > Best regards, > > > Michael > > > > > > > > > P.S.: I know that the way we use this <Body> tag is not the > > > best way to > > > handle csv-like data, but I had to do this because of an > existing file > > > format. > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > Gareth Reakes, Managing Director Parthenon Computing > +44-1865-811184 http://www.parthcomp.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
