Return-Path: 
 <c-user-return-8093-apmail-axis-c-user-archive=axis.apache.org@axis.apache.org>
Delivered-To: apmail-axis-c-user-archive@www.apache.org
Received: (qmail 77298 invoked from network); 30 Jan 2011 12:21:46 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 30 Jan 2011 12:21:46 -0000
Received: (qmail 72987 invoked by uid 500); 30 Jan 2011 12:21:46 -0000
Delivered-To: apmail-axis-c-user-archive@axis.apache.org
Received: (qmail 72773 invoked by uid 500); 30 Jan 2011 12:21:43 -0000
Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:c-user-help@axis.apache.org>
List-Unsubscribe: <mailto:c-user-unsubscribe@axis.apache.org>
List-Post: <mailto:c-user@axis.apache.org>
List-Id: <c-user.axis.apache.org>
Reply-To: "Apache AXIS C User List" <c-user@axis.apache.org>
Delivered-To: mailing list c-user@axis.apache.org
Received: (qmail 72765 invoked by uid 99); 30 Jan 2011 12:21:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jan 2011 12:21:41 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [213.174.32.97] (HELO mailout02.ims-firmen.de) (213.174.32.97)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jan 2011 12:21:34 +0000
Received: from [192.168.1.113] (helo=mailin04.ims-firmen.de)
	by mailout02.ims-firmen.de with esmtp (Exim 4.72)
	(envelope-from <tg@e-tge.de>)
	id 1PjWHI-0002RR-Iw
	for c-user@axis.apache.org; Sun, 30 Jan 2011 13:21:12 +0100
Received: from [217.233.143.66] (helo=[15.136.120.31])
	by mailin04.ims-firmen.de with esmtpa (Exim 4.72)
	(envelope-from <tg@e-tge.de>)
	id 1PjWHI-0006iW-GU
	for c-user@axis.apache.org; Sun, 30 Jan 2011 13:21:12 +0100
Subject: Re: XML reader/writer buffer size problem?
From: Thomas Gentsch <tg@e-tge.de>
To: Apache AXIS C User List <c-user@axis.apache.org>
In-Reply-To: <1296150199.6873.35.camel@parsley>
References: <1276465246.2264.5.camel@parsley>
	 <1276465624.2264.8.camel@parsley>  <4C15A7EA.40706@wso2.com>
	 <1276500772.2268.8.camel@parsley>  <4C15FAE2.9000306@wso2.com>
	 <1276850673.2221.62.camel@parsley>  <1276854782.2221.74.camel@parsley>
	 <1278673353.2367.24.camel@parsley>  <1296129803.2333.124.camel@parsley>
	 <1296130561.2333.126.camel@parsley> <1296146857.6873.28.camel@parsley>
	 <4D41A3AB.1090702@wso2.com>  <1296150199.6873.35.camel@parsley>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 30 Jan 2011 13:21:12 +0100
Message-ID: <1296390072.2333.37.camel@parsley>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
Content-Transfer-Encoding: 7bit


Hi all,

sorry, not Axis' fault ... the input.xml is wrong. Hard to spot, but
there was an opening tag <num50000000> missing.
However
 - still unclear why the two writer types behave that differently ??
 - the error message in the log might be a bit better (my input.xml 
   consists of *one* line of a length of 460000 chars, hence line 1 :-) 
   maybe a char offset might have helped)
I'll update Jira ...

Rgds,
  tge

On Thu, 2011-01-27 at 18:43 +0100, Thomas Gentsch wrote:
> Hi Damitha,
> 
> if you refer to AXIS2C-448 - I have that in.
> 
> Besides of that I haven't found anything :-| (searching for
> axiom_xml_reader or axiom_xml_writer)
> I'll dig more but into it but of course I could save that effort of
> somebody else had an idea :-)
> 
> Also, might be interesting to run that against 1.7 ...
> 
> Rgds + thx,
>   tge
> 
> On Thu, 2011-01-27 at 22:26 +0530, Damitha Kumarage wrote:
> > Hi Thomas,
> > I remember similar problem appeared in a previous thread. Could you 
> > please search in mail archives?
> > 
> > Thanks,
> > Damitha
> > Thomas Gentsch wrote:
> > > Just opened AXIS2C-1534 and attached the test progs + data.
> > > Any help is appreciated!!
> > > Rgds,
> > >   tge
> > >
> > > On Thu, 2011-01-27 at 13:16 +0100, Thomas Gentsch wrote:
> > >   
> > >> Minor correction in the code below (I merged two functions) ...
> > >>
> > >> On Thu, 2011-01-27 at 13:03 +0100, Thomas Gentsch wrote:
> > >>     
> > >>> Hi all,
> > >>>
> > >>> I'm still with Axis2c 1.6 and have a problem (de)serializing an XML
> > >>> string. Is there anything know about such a problem (haven't found
> > >>> anything in Jira)?
> > >>>
> > >>> The essential piece is a string buffer containing an XML structure,
> > >>> which is created from a Tuscany SDO. Then that string buffer gets
> > >>> converted to an Axiom Node (using the Tuscany AxiomHelper) to be
> > >>> returned to the calling Axis2c client. Normally this works nicely, but
> > >>> if the XML is very long (in my example 484460 bytes), it gets truncated.
> > >>>
> > >>> I can see the string buffer "str" (below) as still intact. Then,
> > >>> essentially the following happens:
> > >>> ===========
> > >>> AxiomHelper::toAxiomNode()
> > >>> {
> > >>> ...
> > >>> axiom_xml_reader_t * reader =
> > >>> axiom_xml_reader_create_for_memory(
> > >>>   the_env, (void*)str, strlen(str),
> > >>>   (const axis2_char_t *)"UTF-8", AXIS2_XML_PARSER_TYPE_BUFFER);
> > >>> axiom_stax_builder_t* builder =
> > >>>   axiom_stax_builder_create(the_env, reader);
> > >>> axiom_document_t* document =
> > >>>   axiom_stax_builder_get_document(builder, the_env);
> > >>> axiom_node_t* root_node =
> > >>>   axiom_document_get_root_element(document, the_env);
> > >>> axiom_document_build_all(document, the_env);
> > >>>       
> > >> The code above is function1 and returns "document".
> > >> Below is function2 dealing with that document.
> > >>
> > >>     
> > >>> axiom_node_t* root_node =
> > >>>   axiom_document_get_root_element(doc, the_env);
> > >>> return  root_node;
> > >>> }
> > >>>
> > >>> Now I have the Axiom node "n" and dump it (just for testing):
> > >>>
> > >>> axiom_xml_writer_t * w = axiom_xml_writer_create_for_memory(env,
> > >>>   NULL, AXIS2_TRUE, 0, AXIS2_XML_PARSER_TYPE_BUFFER);
> > >>> axiom_output_t * om_output = axiom_output_create(env, w);
> > >>> axiom_node_serialize(n, env, om_output);
> > >>> axis2_char_t * buf = (axis2_char_t *) axiom_xml_writer_get_xml(w, env);
> > >>>
> > >>> fprintf(f, "\nData: '%s'\n", buf);
> > >>> =============
> > >>>
> > >>> and the output is truncated to 17253 bytes ending with some control
> > >>> characters.
> > >>> As said, that code has been working for months/years now w/o any
> > >>> problems, so I believe that it is OK in general and I rather suspect the
> > >>> Axis2c XML handling in conjunction with large buffers ...
> > >>>
> > >>> I'll extract the pieces into a standalone testprog for easier
> > >>> troubleshooting - but still: Any ideas?
> > >>>
> > >>> Many thx!!!
> > >>>   tge
> > >>>
> > >>>       
> > >>



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