Hi By non-ASCII I meant characters with a value greater than 127. The response that Guththila couldn't parse completely had the french "small letter e with acute accent"; when retrieved from Guththila's internal buffers (and stored in an 'int'), it would yield a negative value.
While googling Guththila, I found that it was supposed to support UTF-8 and UTF-16; according to that, a response containing special french characters should have been properly parsed. Should I conclude that in order to handle UTF-8 encoded requests and responses I should use a different parser? Thank you. Catalina Caloian >>> From: Supun Kamburugamuva <supu...@gmail.com> To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org> Date: 1/30/2009 6:33 AM Subject: Re: guththila_next_char clarification needed Guthtila is written assuming ASCHII characters. So it is not possible to get negative characters. If Guththila gets negative charactes, it means the XML stream has ended or contains invalid characters. Anyway what do you mean by non-ASCII characters? Do you mean binary? Supun. On Thu, Jan 29, 2009 at 8:02 PM, Catalina Caloian < catalina.calo...@quintiq.com> wrote: > Hi > > In the 'guththila_next_char' method, whenever a character is being > retrieved from Guththila's internal char buffers, a check is being made to > see if it has a positive value: > e.g. 'return c >= 0 ? c : -1;' (guththila_xml_parser.c, lines 1522, > 1537, 1616, 1632) > -1 is interpreted as an error code by the caller and the parser basically > stops, deeming the input as invalid. > > I encountered this situation when dealing with a response that contained > some non-ASCII characters. Those non-ASCII characters got stored in > Guththila's buffers of char after a wrap-around of their values, so to fit > in a char. When 'guththila_next_char' got to those characters, it would > encounter negative values and return -1. As a consequence, Axis2C would > treat the response as invalid. > > Replacing the aforementioned 'return' statements with a simple 'return c;' > made Guththila parse the entire response, although the VS XML Visualizer > doesn't display the non-ASCII characters as expected. > > I'm wondering what's the rationale behind Guththila's current way of doing > things. I feel as if I'm missing something, so any help would be highly > appreciated. > > Thank you. > > > Catalina-Georgiana Caloian > Software Engineer > > Quintiq > > T +31 (0) 73 691 07 39 > F +31 (0) 73 691 07 54 > M +31 (0) 65 247 63 99 > E catalina.calo...@quintiq.com > I www.quintiq.com > > > Quintiq Conference "Quintessence 09" Tuesday May 12th, 2009, Country Estate > Duin & Kruidberg, near Amsterdam Schiphol, The Netherlands - for more > information visit www.quintiq.com > > This message contains information that may be privileged or confidential > and is the property of Quintiq. It is only intended for the person to whom > it is addressed. If you are not the intended recipient, you are not > authorized to read, print, retain, copy, disseminate, distribute or use this > message or any part thereof. If you have received this message in error, > please notify the sender immediately and delete all copies of this message. > Please note that e-mails are susceptible to change, therefore they are not > binding. > Quintiq Conference "Quintessence 09" Tuesday May 12th, 2009, Country Estate Duin & Kruidberg, near Amsterdam Schiphol, The Netherlands - for more information visit www.quintiq.com This message contains information that may be privileged or confidential and is the property of Quintiq. It is only intended for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute or use this message or any part thereof. If you have received this message in error, please notify the sender immediately and delete all copies of this message. Please note that e-mails are susceptible to change, therefore they are not binding.
