[
https://issues.apache.org/jira/browse/AXIS2C-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1534.
-------------------------------------
Fix Version/s: 2.0.0
Resolution: Workaround
The guththila implementation of axiom_xml_writer_create() was completely
broken - it allocated memory but never initialized the writer structure
or ops vtable, causing undefined behavior when used. This function has
been broken since its creation and was never properly implemented.
Changes:
- Replace broken implementation with explicit error that returns NULL
and logs a helpful message directing users to use
axiom_xml_writer_create_for_memory() instead
- Fix documentation in om_tutorial.html to use the correct function
and fix the typo (axis2_xml_writer_get_xml -> axiom_xml_writer_get_xml)
The libxml2 parser backend retains a working file-based writer for users
who need that functionality.
> XML writers handle errors differently, add char offset in case of errors
> ------------------------------------------------------------------------
>
> Key: AXIS2C-1534
> URL: https://issues.apache.org/jira/browse/AXIS2C-1534
> Project: Axis2-C
> Issue Type: Bug
> Components: xml/om
> Affects Versions: 1.6.0
> Reporter: Thomas Gentsch
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: axis2xml.tar.gz
>
>
> Have a test prog which reads in an XML doc and prints it put again. With
> large input data sizes (in my example ~400k) the output gets truncated.
> Interestingly the behavior is different when using axiom_xml_writer_create()
> or axiom_xml_writer_create_for_memory().
> With the first
> - the output is ~380k large
> - some error appears in the log file
> whereas with the second
> - the output is only 16k
> - no error
> Attached are two testprogs - tstxml.cpp and tstxml2.cpp with both the xml
> writer types.
> The input and output xml files are contained as well, plus the log file
> mentioned above.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
