Hello Neale;
I suppose the only difference there is that WOTimers don't appear to
occur during a request-response cycle in apps that are not handling
concurrent requests -- as one would expect from the run loop.
Obviously if this behaviour were required, one could emulate it, but
it is nice having it packaged up in the WOTimer.
I filed a bug for this. Even a note in the javadoc would save a fair
bit of time here.
cheers.
I suspect this is almost certainly the case. If 5.2 works anything
like the old Objective-C WebObjects & Foundation then Timers depend
on RunLoops and RunLoops are invoked in the Applications run()
method which is in turn called from main(...)
We've noticed exactly the same behaviour with WOTimers not firing
when deploying under JBoss. I'm looking into solutions but suspect
the easiest will be to port to java Timers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
