Hi
the problem with non-perfect XSD is that its no longer
XSD proper and the whole idea of a world-wide agreed
interface standard collapses.
An official XSD-tool must not support inofficial
XSD-modifications.
Your customer cant Schema-validate his non-perfect XML
with standard tools either
Cheers
Hi
ok, my customer hasn't absolutely perfect XSD and sends to me empty elements
even if their type is int.
I think primary problem is that utility class ConverterUtil and its methods
do not check input parameters for values null or empty string to avoid
useless exceptions like:
java.lang.Runtime
Hi
During tests of Axis2 1.3 parser speed performance for our existing project
we have found big problem in
org.apache.axis2.databinding.utils.ConverterUtil and its convertTo* methods
when processed XML has some empty tags. Convert methods have no code to
test given parameter to 'null' value or v
