Hello Joe;
I have just worked around the problem you have mentioned by parsing-
and-dumping empty cookies in my WOApplication.createRequest(..)
override. It's a crude patch until the next WO version, but it seems
to remove the problem.
cheers.
The cookie issue unfortunately missed that u
The easiest way to customize cookies behavior is to have you own
subclass of WOResponse. There quite a few hooks you can use to
customize the behavior.
Pierre
--
Pierre Frisch
[EMAIL PROTECTED]
On Jan 11, 2008, at 9:59, Joe Moreno wrote:
Pierre,
Thanks for clearing up the cookie
Pierre,
Thanks for clearing up the cookie and time zone issue.
I didn't know the problem with the time zone was a WO bug, I thought
it was an Eclipse bug.
Also, I've tried several different ways to delete the wosid cookie
when I'm terminating a session without any luck.
Can you r
On 11/01/2008, at 5:35 PM, Joe Moreno wrote:
Hi All,
I just upgraded from Tiger client to Leopard and I've noticed two
issues.
First, the Eclipse Console correctly reports the time zone as PST,
but the actual time digits are GMT. Am I missing something? I'm
running Eclipse 3.3.1.1 and
Hi Joe,
Both are known bugs.
The GMT/PST bug will be fixed in the next update of WO.
The cookie issue unfortunately missed that update and will have to
wait for the next one. The issue is that the cookie parsing is too
strict and consider the empty value as a mistake so it trips on
wosid=
Hi All,
I just upgraded from Tiger client to Leopard and I've noticed two
issues.
First, the Eclipse Console correctly reports the time zone as PST,
but the actual time digits are GMT. Am I missing something? I'm
running Eclipse 3.3.1.1 and WOLips 3.3.4574.
Second, I keep getting An
