[
https://issues.apache.org/jira/browse/AXIS2-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847288#action_12847288
]
Mauro Molinari commented on AXIS2-4075:
---------------------------------------
So, it seems to be a problem with java2wsdl.
I use contract first approach, so I'm writing my own WSDLs and using wsdl2java.
As I said, my case, every xs:date is mapped to java.util.Date, while every
xs:dateTime is mapped to java.util.Calendar. At runtime, Axis2 takes care of
the conversions, in both directions.
So, manually changing the WSDLs, as Lucas suggests, seems to be the correct
workaround for this. However, I would have said the change were required for
both requests and responses.
> AXIS2 1.4.1 does not support java.util.Date type
> ------------------------------------------------
>
> Key: AXIS2-4075
> URL: https://issues.apache.org/jira/browse/AXIS2-4075
> Project: Axis2
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.4.1
> Environment: windows xp sp2 + tomcat 5.5 + java 1.5 + axis2 1.4.1
> Reporter: yong yang
> Attachments: DateService.aar, DateService.java, DateService.wsdl,
> exception.txt
>
>
> Hi, I found that the axis2 1.4.1 does not support java.util.Date type.
> 1)WSDL
> AXIS2 1.4.1 should map java.util.Date to xs:date in the WSDL, rahter than
> xs:dateTime(see the attached wsdl).
> 2)deserialize and serialize ISO xml DATE string
> AXIS2 1.4.1 can not construct a java.util.Date object from a ISO xml date
> string, for example, "2001-01-01". It threw an exception, "date string can
> not be less than 19 charactors". (more detail can be found in the attached
> exception.txt).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
