Re: multiple scheduled WOTimer objects
Re: multiple scheduled WOTimer objects
- Subject: Re: multiple scheduled WOTimer objects
- From: Travis Britt <email@hidden>
- Date: Mon, 17 Nov 2003 14:52:15 -0500
On Nov 16, 2003, at 3:17 PM, Hsu wrote:
Unless there is a strong reason to use WOTimer (there isn't) try using
java.util.Timer instead.
Yep yep.
That said, this should work fine. Do you have a simple example?
I figured out what was happening: when scheduling WOTimers on identical
targets/selectors only the first fires. Until the first timer fires,
subsequent timers act like they're successfully scheduled but then
never fire. (By identical I mean the same object - one stored in a
Session, for example.) If a new object is instantiated for each WOTimer
then all timers fire.
But I ended up just creating a new class that does what I need,
implementing java.util.Timer.
tb
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.