That's cool. Thanks for providing the complete fix.
BTW, Can someone tell me when the Axis C++ 1.6 Final
version is going to be released ?
--- Nadir Amra <[EMAIL PROTECTED]> wrote:
> A more complete fix has been implemented, including
> a new method,
> canParseMore() in the abstract base clas
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
Yes, I think I just took the easy way out :-) I did recognize the fact
that we should have the variable around as a state variable. Let me look
into this a little more.
Nadir K. Amra
Kamlesh kumar <[EMAIL PROTECTED]> wrote on 08/12/2006 01:38:42 PM:
> Hey,
> Thanks for providing the fix.
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 cra
I have fixed this problem. See AXISCPP-770 for details. Please try and
see if your problem persists by downloading code and testing.
Nadir K. Amra
Kamlesh kumar <[EMAIL PROTECTED]> wrote on 08/11/2006 09:41:21 PM:
> The current implementation of XMLParserXerces ignores
> the value returne
The current implementation of XMLParserXerces ignores
the value returned by the parseNext() call, this
causes the program to crash the next time parseNext()
is called.
Here is a sample code inside the peek function
illustrating the problem.
AnyElement* elem = m_Xhandler.getAnyElement();
