On 09/01/2009, at 3:10 AM, Ken Anderson wrote:
I do exactly what you're doing all the time, and I do not have the
issue you're experiencing. One thing I do at the beginning of my
WOApplication subclass is this:
TimeZone.setDefault(TimeZone.getTimeZone("GMT"));
Mike-
That worked. Thnx! The error had nothing to do with the model.
Your fix revealed the error to be "Path must include project and resource
name."
I cleaned up an incorrect entry I had made in the Configure Build Path -->
Source. Removing that up took care of the problem.
Thnx.
--JSt
On
List,
I have now updated my build.xml file from a new dummy application
created using the latest WOLips as advised in the WOLips blog for the
new hotness. I also did this for my WO framework that contains the
jars I need to link in to, using a new dummy framework.
Now I get sight of my pr
Bardi,
I do exactly what you're doing all the time, and I do not have the
issue you're experiencing. One thing I do at the beginning of my
WOApplication subclass is this:
TimeZone.setDefault(TimeZone.getTimeZone("GMT"));
NSTimeZone.setDefault(TimeZone.getTim
| a fix is committed
That means it will be available tomorrow after the next nightly build?
Well, actually it should have been in last night's build, but it looks
like the sourceforge cert expired so our build server was hanging
waiting for me to accept the new cert ... So it's building now.
Lachlan,
Many thanks for your reply. I have updated to the latest Eclipse 3.4.1
and the latest WOLips nightly, but that does not resolve this issue. I
am also posting to the rome mailing list to try from that angle, but a
nightly build of the latest rome jar didn't help either.
I also tri
Bug ID 6342679: NSTimestamp Happy New Year Bug
I think that I am being stonewalled.
I have had this bug reopened once.
I do not believe that this bug has to do with
timezones at all.
Even so
UTC and GMT are effectively the same. Not?
Comments please.
Best regards,
Bardi
-Original Messag
