Hello
The following snippet taken from a generated deserialize method may lead to a
memory leak:
axutil_hash_index_t *hi;
for (hi = axutil_hash_first(attribute_hash, env); hi; hi =
axutil_hash_next(env, hi))
{
axutil_hash_this(hi, key, NULL, val);
Hi
In the 'guththila_next_char' method, whenever a character is being retrieved
from Guththila's internal char buffers, a check is being made to see if it has
a positive value:
e.g. 'return c = 0 ? c : -1;' (guththila_xml_parser.c, lines 1522,
1537, 1616, 1632)
-1 is interpreted as an
.
Catalina Caloian
From: Supun Kamburugamuva supu...@gmail.com
To: Apache AXIS C Developers List axis-c-dev@ws.apache.org
Date: 1/30/2009 6:33 AM
Subject:Re: guththila_next_char clarification needed
Guthtila is written assuming ASCHII characters. So it is not possible to get
negative
Hello
Scenario:
- an application needs to use two services - let's call their
respective wsdl files Mapping.wsdl and Geocoding.wsdl
- both services use a type called Coordinate
- upon generating C code from the wsdl files using WSDL2C, we get two
adb_Coordinate.c and two
Hi.
The patch you've attached seems to solve the problem.
Unfortunately, it introduces another bug as a side-effect: now, a 'current_node
= first_node;' assignment also happens in the deserialization of structures
deduced from the simpleTypes of a wsdl. This leads to compilation errors
Components: code generation
Environment: Windows XP
axis2-1.4.1-src with slight changes to the CADBBeanTemplateSource.xsl template
to embed some minor bug fixes.
Reporter: Catalina Caloian
Scenario:
- the first element in a sequence is nillable
