Re: Accessing the session in WOLongResponsePage.performAction
Re: Accessing the session in WOLongResponsePage.performAction
- Subject: Re: Accessing the session in WOLongResponsePage.performAction
- From: Helge Staedtler <email@hidden>
- Date: Wed, 08 Feb 2006 18:08:55 +0100
Title: Re: Accessing the session in WOLongResponsePage.performAction
hi!
Perhaps this stuff i postted some time ago at wocode.com might help you with the longresponse:
http://WOCode.com/cgi-bin/WebObjects/WOCode.woa/wa/ShareCodeItem?itemId=291
You will find an enhanced version of this code in action in the *brandnew* NoxymoCore Framework for WebObjects which also sports a nice wrappercomponent fro longresponse-status-displaying. More Information is available here:
http://www.noxymo.com/product_noxymocore.html
regards,
helge
Am 08.02.2006 17:38 Uhr schrieb "Jerry W. Walker" unter <email@hidden>:
Hi, Fabrice,
The API documentation for WOLongResponsePage is generally inadequate for using the component. However, Apple has provided a nice example with the Developer distribution at:
/Developer/Examples/JavaWebObjects/LongRequest/
There is a nice Readme.html document in the project's directory that you can open directly in your browser for some general overview documentation.
It will help more, however, if you build, run and review that example. You'll note the following comment in the displayed Main page:
This example application demonstrates the creation and use of long
running request/response pages which enables web-based applications
to perform lengthy tasks while providing feedback and means of
interruption to the user. This example will demonstrate six
different scenarios of long requests, from the very basic just
showing progression to the very robust, giving cancelling options and
sending e-mail upon competition.
In particular, when you build and run the app, click on the link that's labeled "Refresh with Data Information, Progress bar and live data." Then check the code for that component.
Good luck.
Regards,
Jerry
On Feb 8, 2006, at 7:58 AM, Fabrice Pipart wrote:
I have to admit, I don't remember the Observer pattern very well ;-)
But if I don't make any mistake, the "separate thread's monitoring class" you talk about is where my WOLongResponsePage's performAction is executed. And to be an Observer of the Session, it needs to have access to the Session doesn't it?
And it is what I can't manage to do without having an error in the console :-(
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Helge Städtler
- Expect and Respect.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden