[
https://issues.apache.org/jira/browse/OFBIZ-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783261#action_12783261
]
Mike Fanning commented on OFBIZ-2139:
-------------------------------------
I ran into this issue while exporting services. It's not just a matter of one
timestamp format or another, the SOAP handler passes all the parameters to the
service as strings, which then causes the exception. I have a patch for this
issue, but it doesn't directly address Adil's options. Should I attach it to
this issue?
> Service validation doesnt accept timestamp format 2009-01-15T00:00:00.000Z
> ---------------------------------------------------------------------------
>
> Key: OFBIZ-2139
> URL: https://issues.apache.org/jira/browse/OFBIZ-2139
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Environment: WinXP / JDK1.6 / Postgre8.3
> Reporter: Adil BEN EL KHATTAB
>
> When I request a value of type timestamp through a SOAP service call, the
> value returned has the format '2009-01-15T00:00:00.000Z'. When I return the
> same value as IN parameter to another service for updating the same field the
> value is not accepted as a valid timestamp.
> Error is:
> 2009-01-25 18:54:44,919 (TP-Processor3) [ RequestHandler.java:326:ERROR]
> Request SOAPService caused an error with the following message: Error calling
> event: org.ofbiz.webapp.event.EventHandlerException: Type check failed for
> field [updateRelative.thruDate]; expected type is [java.sql.Timestamp];
> actual type is [java.lang.String] (Type check failed for field
> [updateRelative.thruDate]; expected type is [java.sql.Timestamp]; actual type
> is [java.lang.String])
> Expected behavior > 2 options:
> 1. format 2009-01-15T00:00:00.000Z should be accepted as a valid timestamp
> 2. timestamp should be returned by SOAP service as '2009-01-15 00:00:00.000'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
