RE: Handling Dates in websphere before 1940 causing issue

How would that make problems for dates in 1939? Just out of curiosity :)

In any case, sounds like a good candidate for including in your CheckStyle
or Findbugs testing harness. Such a thing requires static code analysis -
cannot be done easily at runtime.


-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Ashish Kulkarni
Sent: 8. juli 2010 15:22
To: Java Programming on and around the iSeries / AS400
Subject: Re: Handling Dates in websphere before 1940 causing issue

Hi
Thanks for the update, we found what was causing issue, our websphere has
timezone set to EST5EDT, but some programs had hard coded time zone as
America/New_York in programs which was causing issues.

On Tue, Jul 6, 2010 at 1:32 PM, CJPB - MENDEZ GLADYS
<gmendez@xxxxxxxxxxx>wrote:

Hi Ashish:
We deal with this problem on websphere 6.1. At the administrative console
of websphere server,
go to Resources, JDBC, Data Sources, then select your datasource name.
Next, select Personalized Properties, and insert value "iso" dateFormat
property.

I hope this could help you

Regards

Gladys Méndez
Caja Bancaria
Montevideo, Uruguay



-----Mensaje original-----

message: 4
date: Tue, 6 Jul 2010 09:38:53 -0400
from: Ashish Kulkarni <ashish.kulkarni13@xxxxxxxxx>
subject: Handling Dates in websphere before 1940 causing issue

Hi
Has anyone seen issue with dates if the date is before 1940? We have this
jsf application where we map date from screen to backingbean,
If i enter 09/03/1939, my backing bean gets date 09/02/1939.

Has anyone seen this issue, we are on websphere 6.1 on AS400 V6R1

--
Ashish
www.ayurwellness.com
www.mysoftwareneeds.com


------------------------------

message: 5
date: Tue, 06 Jul 2010 08:44:48 -0500
from: David Gibbs <david@xxxxxxxxxxxx>
subject: Re: Optimize java to run on AS400

Ashish Kulkarni wrote:

We are on V6R1 and just turned on 64 bit on AS400

If you're using the 64bit JVM, then you're using the PASE based JVM ...

and

I don't think you need to do anything to optimize the bytecode.

At one time, with the classic JVM, you could run the CRTJVAPGM command to
pre-create the native code that was attached to the byte code. But I

think

the need for that mostly went away in later releases.

david

--
IBM i on Power Systems - For when you can't afford to be out of business


------------------------------

message: 6
date: Tue, 06 Jul 2010 09:18:42 -0600
from: Pete Helgren <Pete@xxxxxxxxxx>
subject: Re: Optimize java to run on AS400

Ashish,

David went where I was going to go. If you are on the more recent
versions of the OS, you shouldn't have to optimize. Also, as I
understand it, the 64bit "classic" version is going away in IBM i 7.1.

The 32bit JVM has performed very well in my Tomcat and JRuby
applications (Glassfish) on i. Not sure what WAS is best optimized for.

Pete


On 7/6/2010 7:44 AM, David Gibbs wrote:

Ashish Kulkarni wrote:

We are on V6R1 and just turned on 64 bit on AS400

If you're using the 64bit JVM, then you're using the PASE based JVM ...

and I don't think you need to do anything to optimize the bytecode.

At one time, with the classic JVM, you could run the CRTJVAPGM command

to

pre-create the native code that was attached to the byte code. But I

think

the need for that mostly went away in later releases.

david

------------------------------

--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
digest list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.



End of JAVA400-L Digest, Vol 8, Issue 92
****************************************


--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.