Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-dev@incubator.apache.org
Message-ID: <404586353.1221749084652.JavaMail.jira@brutus>
Date: Thu, 18 Sep 2008 07:44:44 -0700 (PDT)
From: "David Calavera (JIRA)" <jira@apache.org>
To: abdera-dev@incubator.apache.org
Subject: [jira] Commented: (ABDERA-199) [core] AtomDate does not check for
 Date Constructs having T & Z  separations between Date and Time
In-Reply-To: <1453171244.1220961344443.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ABDERA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632231#action_12632231 ] 

David Calavera commented on ABDERA-199:
---------------------------------------

This patch breaks several tests. Can you fix these tests and submit the patch again?

Thank you.

> [core] AtomDate does not check for Date Constructs having T & Z  separations between Date and Time 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ABDERA-199
>                 URL: https://issues.apache.org/jira/browse/ABDERA-199
>             Project: Abdera
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Amit Surana
>            Priority: Minor
>         Attachments: patch.txt
>
>
> In RFC4287: Date Consturcts Section, its mentioned that - A Date construct is an element whose content MUST conform to the "date-time" production in [RFC3339].  In addition, an uppercase *"T" character MUST* be used to separate date and time, and an uppercase *"Z" character MUST* be present in the absence of a numeric time zone offset.
> But in the org.apache.abdera.model.AtomDate Implementation, When the Date is passed as String, I saw that the PATTERN does not check if the Date Format entered has T or Z.
> I Tested the Pattern in a sample program.
> I gave certain WRONG Inputs like -> "2008-09-08A20:00:00B+05:30"  or "2008-09-08X23:30:00Y", etc
> Instead of getting InvalidDateFormat Exception, I got the output as some Irrelevant date.

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