You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Hitesh Shah <hs...@aalayance.com> on 2002/10/23 00:23:40 UTC
java.sql.Timestamp
We have some java classes that we need Axis to move about. Some of them
have attributes of type java.sql.Timestamp
I noticed that Axis changes these types to java.util.Calendar when I run
java org.apache.axis.wsdl.WSDL2Java. This is throwing off our code that
accesses these classes.
It is kind of odd that Axis modifies the class definition itself - I had
expected it to generate wrapper classes with SOAP friendly types rather
than modify our actual class itself. Has anyone faced a similar issue
and if so what is the solution (to not use WSDL2Java and code client and
server stubs by hand?)
Thanks
Hitesh
Re: java.sql.Timestamp
Posted by vairamuthu thayapavan <vt...@vijayaba.cse.mrt.ac.lk>.
hi!
actually in the default type mapping, XSD_TIME is mapped to the
org.apache.axis.types.Time class as shown below. this type class use the
java.util.Calendar. So what is happening here is, ur java.sql.Timestamp is
mapped to the XSD_TIME and again it mapped to the java.util.Calendar not to
the java.sql.Timestamp.
myRegister(Constants.XSD_TIME, org.apache.axis.types.Time.class,
new SimpleSerializerFactory(org.apache.axis.types.Time.class,
Constants.XSD_TIME),
new SimpleDeserializerFactory(org.apache.axis.types.Time.class,
Constants.XSD_TIME)
regards
vtpavan
----- Original Message -----
From: "Hitesh Shah" <hs...@aalayance.com>
To: <ax...@ws.apache.org>
Sent: Wednesday, October 23, 2002 4:23 AM
Subject: java.sql.Timestamp
> We have some java classes that we need Axis to move about. Some of them
> have attributes of type java.sql.Timestamp
>
> I noticed that Axis changes these types to java.util.Calendar when I run
> java org.apache.axis.wsdl.WSDL2Java. This is throwing off our code that
> accesses these classes.
>
> It is kind of odd that Axis modifies the class definition itself - I had
> expected it to generate wrapper classes with SOAP friendly types rather
> than modify our actual class itself. Has anyone faced a similar issue
> and if so what is the solution (to not use WSDL2Java and code client and
> server stubs by hand?)
>
> Thanks
> Hitesh
>
>