Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Message-ID: <3F550979.5020800@iseran.com>
Date: Tue, 02 Sep 2003 14:19:53 -0700
From: Steve Loughran <steve_l@iseran.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: Timestamp attribute processing
References: <D466FBEAA19E7E408BE3FAAC6EEB5676023FF85A@utah.ignitemedia.com>
 <D466FBEAA19E7E408BE3FAAC6EEB5676023FF85A@utah.ignitemedia.com>
 <5.2.1.1.0.20030902142805.02a6a008@mail.comcast.net>
In-Reply-To: <5.2.1.1.0.20030902142805.02a6a008@mail.comcast.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Ken Gentle wrote:
> At 12:56 PM 9/2/2003, you wrote:
> 
>> Steve Cohen wrote:
>>
>>> Hmm, that's weaker than I would have expected.  If I'd like something 
>>> a little better, is your recommendation then to add to DateUtils?
>>
>>
>> I guess it is time for a date type. I imagine taking 
>> java.util.Calendar as a param would be a nice way to map it (or Date, 
>> though that one's lack of timezones is an eternal source of trouble in 
>> the SOAP world)
> 
> 
> SOAP and everywhere an application may span timezones.

> Anyway, I'd suggest be very cautious about introducing general date 
> processing in ant that would allow arbitrary date formats, as opposed to 
> one or two formats per locale, or a single ISO style format 
> "yyyy-MM-ddTHH:mm:ss.SSS" (I think that one is legal, I don't have the 
> spec in front of me).

I agree, with the caveat that the 'T' is so vague; there is nowhere in 
the ISO spec to say 'dont know the timezone', which is why I use time_t 
in GMT as the sole time specifier in my soap systems


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org