Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <744221743.299531266331347945.JavaMail.jira@brutus.apache.org>
Date: Tue, 16 Feb 2010 14:42:27 +0000 (UTC)
From: "Bernhard Schauer (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS2-4626) Wrong Date handling in
 SimpleTypeMapper
In-Reply-To: <1496971823.299501266331228197.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernhard Schauer updated AXIS2-4626:
------------------------------------

    Description: 
Class SimpleTypeMapper

  Line 113 to 115:

        } else if (name.equals(W_DATE)) {
            return makeDate(text);
        }

  Line 312 to 314:

    public static Object makeDate(String source) {
        return ConverterUtil.convertToDateTime(source).getTime();
    }

I think the latter should return the result from ConverterUtil.convertToDate(source) not from convertToDateTime. If that is not possible, I'd expect ConverterUtil.convertToDateTime to also accept a date in the format "yyyy-mm-dd" not only in the long 19 character version? or am I wrong here? 

As Axis2 serializes Date Objects in my case (POJO Webservice) in the "yyyy-mm-dd" format to String, this format should definitely be accepted on clientside in my opinion.

  was:
Class SimpleTypeMapper

  Line 113 to 115:

        } else if (name.equals(W_DATE)) {
            return makeDate(text);
        }

  Line 312 to 314:

    public static Object makeDate(String source) {
        return ConverterUtil.convertToDateTime(source).getTime();
    }

I think the latter should return the result from ConverterUtil.convertToDate(source) not from convertToDateTime. If that is not possible, I'd expect ConverterUtil.convertToDateTime to also accept a date in the format "yyyy-mm-dd" not only in the long 19 character version? or am I wrong here?


> Wrong Date handling in SimpleTypeMapper
> ---------------------------------------
>
>                 Key: AXIS2-4626
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4626
>             Project: Axis2
>          Issue Type: Bug
>          Components: databinding
>    Affects Versions: 1.5.1
>         Environment: Not relevant
>            Reporter: Bernhard Schauer
>
> Class SimpleTypeMapper
>   Line 113 to 115:
>         } else if (name.equals(W_DATE)) {
>             return makeDate(text);
>         }
>   Line 312 to 314:
>     public static Object makeDate(String source) {
>         return ConverterUtil.convertToDateTime(source).getTime();
>     }
> I think the latter should return the result from ConverterUtil.convertToDate(source) not from convertToDateTime. If that is not possible, I'd expect ConverterUtil.convertToDateTime to also accept a date in the format "yyyy-mm-dd" not only in the long 19 character version? or am I wrong here? 
> As Axis2 serializes Date Objects in my case (POJO Webservice) in the "yyyy-mm-dd" format to String, this format should definitely be accepted on clientside in my opinion.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.