A more complete fix has been implemented, including a new method, canParseMore() in the abstract base class that may be utilized in the future. Basically bCanParseMore is saved in the class so that it is kept across invocations...
Nadir K. Amra Kamlesh kumar <[EMAIL PROTECTED]> wrote on 08/12/2006 01:38:42 PM: > Hey, > Thanks for providing the fix. Its better than before > but I see that there might still be some issues with > the new code. The problem is that the previous value > of bCanParseMore is lost when the next time someone > invokes next() function on XMLParserXerces and so it > can cause the program to crash. (Currently, we assume > that its always ok to call the m_pParser->next the > first time, however its not a safe assumption. There > are places in SoapDeSerializer where in we ignore the > return value of next and so no way of knowing that we > have reached the end of stream) > > If we have bCanParseMore as a class member variable > then we can avoid this issue. This value can be > initialized with the return value of > m_parser->parseFirst. > > Let me know if I am not clear and I can try to provide > more details. > > Thanks > -Kamlesh > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
