axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "S.Uthaiyashankar (JIRA)" <>
Subject [jira] Resolved: (AXIS2C-1356) Text longer than 128K silently discarded with guththila parser
Date Thu, 10 Sep 2009 11:44:57 GMT


S.Uthaiyashankar resolved AXIS2C-1356.

       Resolution: Fixed
    Fix Version/s: Next Version

Fixed in revision 813383

> Text longer than 128K silently discarded with guththila parser
> --------------------------------------------------------------
>                 Key: AXIS2C-1356
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: guththila
>    Affects Versions: 1.5.0
>         Environment: Linux, Apache, Axis2 C service
>            Reporter: Emanuele Benedetti
>            Assignee: S.Uthaiyashankar
>             Fix For: Next Version
> I created a services in C/C++ under Linux using the Axis2/c framework.
> The service have one function which takes one string parameter. I run the service using
the Apache axis module.
> The soap xml message is similar to the following (checked with tcpmon):
> <s:Envelope xmlns:s="">
> <s:Body xmlns:xsi="" xmlns:xsd="">
> <Receive xmlns="">
> <updategram>long text string</updategram>
> </Receive>
> </s:Body>
> </s:Envelope> 
> If the long text string in the <updategram> element is longer than 128K, in the
call to the main serivice procedure (the one assigned to axis2_svc_skeleton_ops::invoke and
called by the axis2 engine), the node parameter (third parameter of type axiom_node_t *) 
have the following structure:
> <Receive><updategram></updategram></Receive>
> that is the <updategram> is empty. There is no error in any log. The <updategram>
is discarded.
> This happen only if the axis2c framework is configured with the default options. That
is, the guththila parser is used (it is on by default). If I configure axis2 with the --enable-libxml2,
everything is working fine.
> So it seem to be a limit in the guththila parser.
> Grretings

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message