You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Dinesh Premalal <xy...@gmail.com> on 2008/02/28 05:15:33 UTC

[Axis2]Making Guththila default parser (Re: [Vote][Axis2]Axis2/C 1.3.0 Release Artifacts)

Bill,

"Bill Mitchell" <bm...@austin.rr.com> writes:

> Dinesh, I noticed when I unzipped the 1.3 build that there was no
> guththila.dll, which implies to me that it was still built with libxml2 as the
> parser.  As there are no open guththila Jira reports, I don’t think there is
> any reason guththila can’t be the default parser.  Even though this was raised
> as a suggestion a month ago, my guess is that no one remembered, after all the
> issues were fixed, to go ahead and change over the default. 

I guess what we had was a discussion regarding make guththila default
parser, and no decisions made regarding that. Although all the issues
were fixed, lets give sometime to module implementers to play with
Guththila as the default parser.

> It’s probably too late at this point to switch, but I wanted to bring it to
> your attention.  It may be that during the 1.3 development cycle, guththila
> actually received more use and testing than did the libxml
> interface.
Even though it was well tested with Axis2/C scenarios , I think
guththila is still didn't test much with other modules (like
Rampart/C, Sandesha/C, Savan/C etc). I would suggest to move forward
with making Guththila default parser after having feedback from other
module developers. 

thanks,
Dinesh
-- 
http://nethu.org


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org

Re: [Axis2]Making Guththila default parser (Re: [Vote][Axis2]Axis2/C 1.3.0 Release Artifacts)

Posted by Senaka Fernando <se...@wso2.com>.
> Bill,
>
> "Bill Mitchell" <bm...@austin.rr.com> writes:
>
>> Dinesh, I noticed when I unzipped the 1.3 build that there was no
>> guththila.dll, which implies to me that it was still built with libxml2
>> as the
>> parser.  As there are no open guththila Jira reports, I don’t think
>> there is
>> any reason guththila can’t be the default parser.  Even though this
>> was raised
>> as a suggestion a month ago, my guess is that no one remembered, after
>> all the
>> issues were fixed, to go ahead and change over the default.Â
>
> I guess what we had was a discussion regarding make guththila default
> parser, and no decisions made regarding that. Although all the issues
> were fixed, lets give sometime to module implementers to play with
> Guththila as the default parser.
>
>> It’s probably too late at this point to switch, but I wanted to bring
>> it to
>> your attention.  It may be that during the 1.3 development cycle,
>> guththila
>> actually received more use and testing than did the libxml
>> interface.
> Even though it was well tested with Axis2/C scenarios , I think
> guththila is still didn't test much with other modules (like
> Rampart/C, Sandesha/C, Savan/C etc). I would suggest to move forward
> with making Guththila default parser after having feedback from other
> module developers.

+1,

Regards,
Senaka

>
> thanks,
> Dinesh
> --
> http://nethu.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org