Hi,

I'm wondering what the best practice is for handling beans that contain
methods returning java.util.Locale or java.util.TimeZone.  I'm currently
using Axis 1.2RC1.

This relates to messages from Java2WSDL such as:

[WARN] Types - -The class java.util.Locale is defined in a java or javax
package and cannot be converted into an xml schema type.  An xml schema
anyType will be used to define this class in the wsdl file. [WARN] Types
- -The class java.util.TimeZone is defined in a java or javax package
and cannot be converted into an xml schema type.  An xml schema anyType
will be used to define this class in the wsdl file. [WARN] Types - -The
class java.security.Key is defined in a java or javax package and cannot
be converted into an xml schema type.  An xml schema anyType will be
used to define this class in the wsdl file.

Java2WSDL seems to generate an invalid WSDL in this case.  Curiously, it
seems that the first time it encounters a Locale, it "dodges the bullet"
by defining the element as xsd:anyType, but for some reason on the next
appearance of Locale, it types it as tns5:Locale, where tns5 is
namespace "http://util.java";.  This fails as there are no types defined
for this namespace in the WSDL.

Q's.  Is there a better way of handling these unmapped types?  Am I
forced to write custom Serializer/DeSerializer, or is there one in
existence to handle these types already?

TIA

Brett Randall

Reply via email to