From: <Saa...@Co...> - 2006-12-28 17:12:38
|
<html><head><META HTTP-EQUIV=3D"Cache-control" CONTENT=3D"no-cache"><META = HTTP-EQUIV=3D"Pragma" CONTENT=3D"no-cache"></head><body = bgcolor=3D"white"><P>Hi</P> <P>ddsteps version 1.1.1-beta2</P> <P>An excel date comes back as one day previous in java.util.Date in my = application. <BR>According to the jxl faq its due to a GMT TimeZone used by= = jxl and local TimeZone <BR>used by the application = ref=3Dhttp://www.andykhan.com/jexcelapi/tutorial.html#dates. <BR>There is n= o= fix provided by jxl since its upto the client app to handle the date = without <BR>the GMT timezone. In an effort to get my unit test to work I = digged a little further <BR>in ddsteps code to get the correct date. </P> <P>I made the change at org.ddsteps.dataset.excel.getValue() line # 102. = with the following code.</P> <P>...<BR>DateCell dateCell =3D (DateCell) cell;<BR>String pattern =3D = ((SimpleDateFormat)dateCell.getDateFormat()).toPattern();<BR>SimpleDateForm= at= sdf =3D new SimpleDateFormat(pattern);<BR>Date date=3Dnull;<BR>try = {<BR> date =3D sdf.parse(dateCell.getContents());<BR>} catch = (ParseException e) {<BR> throw new RuntimeException();<BR>}</P> <P>return date;<BR>...</P> <P>Since I dont know if this is the right place and/or prefered type o= =66= fix. <BR>How and when can I get a fix for ddsteps for this problem=3F Do I= = need to create an issue in jira=3F</P> <P>Thanks<BR>Saad.</P> <P><pre = wrap>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Confidentiality Notice: The information contained in and transmitted with = this communication is strictly confidential, is intended only for the use o= =66= the intended recipient, and is the property of Countrywide Financial = Corporation or its affiliates and subsidiaries. If you are not the intende= d= recipient, you are hereby notified that any use of the information = contained in or transmitted with the communication or dissemination, = distribution, or copying of this communication is strictly prohibited by = law. If you have received this communication in error, please immediately = return this communication to the sender and delete the original message and= = any copy of it in your possession. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </pre></P></body></html> |