Dvae Mount wrote:
>
> Thanks for the info. Guess you'd have to wrap Date to get a good Time
> class. In the case I'm looking at, the vendor splits date and time into
> separate fields. Okay for .NET, too bad for Java (and me).
It is quite possible for you to write a serializer and deserializer
nt: Friday, April 26, 2002 6:09 AM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2java error with .NET WSDL
There's a simple answer for you, but you won't like it. AXIS doesn't yet
support xsd:time. We support dateTime but not time. Not sure what we'd
map it to in Java. Suggestions?
lto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 6:09 AM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2java error with .NET WSDL
I think the problem is because Axis only handles a subset of
the XML Schema data types. The JAX-RPC spec specifies the
XML Schema data types that a JAX-RPC implementation are r
/2002 06:59:05 PM
Please respond to [EMAIL PROTECTED]
To:"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject:RE: WSDL2java error with .NET WSDL
I am having similar trouble with a .NET WSDL file for a different set of
web
services.
java.io.IOException: Type http:
rvice also which doesn't sound like it in your case.
>From: "Mount, Dave" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: RE: WSDL2java error with .NET WSDL
>Date: T
I am having similar trouble with a .NET WSDL file for a different set of web
services.
java.io.IOException: Type http://www.w3.org/2001/XMLSchema:time is
referenced but not defined.
at org.apache.axis.wsdl.toJava.SymbolTable.checkForUndefined(Unknown
Source)
at org.apache.axis.w
