Hi all,
while testing a web service with different variations (regarding "nillable" and
"minOccurs")
of input and output parameters, I discovered a few cases where the SOAP
response or the Java
input object passed by Axis appears to be wrong (or at least questionable). For
the complete table,
s
Hi all,
given the following web service method implementation:
public String[] getString() {
return null;
}
with the following response element definition from the WSDL (used by
WSDL2Java):
Hi,
after additional experiments, it seems that the described problem appears for
primitives inside container types, but not for primitives that are directly
exposed on the interface. For example, a boolean with the WSDL attributes
nillable="false" and minOccurs="1" results in a primitive type
Hi all,
the -Euwc option (introduced in
https://issues.apache.org/jira/browse/AXIS2-3353) of
org.apache.axis2.wsdl.WSDL2Java generates wrappers for nillable
(nillable="true") or optional (minOccurs="0") elements. However, it also
generates wrappers for types that are neither nillable nor optio
Hi all,
when a string element in a response object is declared with nillable="true" and
minOccurs="1" in the WSDL,
but the element is not explicitly initialized to null in the service
implementation code, the element
is not included in the response message (violating the WSDL). Expected:
xsi:ni
