Thanks George. I was doing same, debugging the code, and trying to pull odd man out ;-)
I think I have finally found the issue of LongResponsePage not getting refreshed. In the performAction() method the business logic is LOCKING the session's defaultEditingContext and performing the business operation and soon after this LongResponsePage thread is blocking and failing to refresh.
Once, LongResponsePage operation thrown an error of editingContext is not locked. So, I locked it and unlocked it as well!!!
Am wondering how should I perform my business operation without locking my editingContext?
I see that we should setup a wiki page dedicated to LongResponsePage page caveats, pros, cons, issues, usage examples, best practices,...!
Thank You,
Shravan Kumar. M
--- On Sat, 7/25/09, George Domurot
<email@hidden> wrote:
From: George Domurot <email@hidden>
Subject: Re: WOLongResponsePage issues
To: "Shravan Kumar. M" <email@hidden>
Cc: email@hidden
Date: Saturday, July 25, 2009, 3:31 AM
Shravan, do you have a custom page wrapper that is performing and special tricks?
If you have a simple example working, try taking an exact duplicate of the example and using it within your project. Make sure you don't add any additional code or components, and make sure it still works as expected. If so, start layering in your code a little bit at a time until it breaks.
-George On Jul 24, 2009, at 11:59 AM, Shravan Kumar. M wrote: Hello Group,
I have simulated the Long response code from my app to a sample project and Long response is performing perfect there... but NOT in my app, i.e., in my app long response page is not refreshing and returning no instance page.
I see that there should be some setting or some configuration in my app that is causing long response to NOT work correctly... I am still trying to extract this thing... could any one help me what am I missing/ should look at?
Thank You,
Shravan Kumar. M
------------------------------
--- On Fri, 7/24/09, email@hidden <email@hidden> wrote:
From: email@hidden <email@hidden>
Subject: Re: WOLongResponsePage
issues
To: "shravan kumar" <email@hidden>
Cc: email@hidden
Date: Friday, July 24, 2009, 1:11 PM
With use both prototype and jQuery (in compatibilty mode) without any problems. But I never used WOLongResponsePage so I can not compare them. Maybe someone could give you a progress bar thread implementation/example dealing with sessio nand editing context Jérémy
-----shravan kumar <email@hidden> a écrit : -----
A : email@hidden
De : shravan kumar <email@hidden>
Date : 24/07/2009 09:24
cc:
email@hidden
Objet : Re: WOLongResponsePage issues
Thanks for your response Jérémy . But as my business logic is very much tied with session, editing context, I may need WOLongResponsePage.
Also, I have NOT integrated Project Wonder to my system and I only use few of Project Wonder components here and there in my application. I hope to use AjaxProgressBar I have to at least integrate Project Wonder's AJAX framework (we know jQuery, we like it and we use it, but not Prototype.js which is the core of Project Wonder's Ajax framework, sorry! for my privileges).
Correct me if am wrong?
Thank You,
Shravan Kumar. M
-------------------------------------
--- On Fri, 7/24/09, email@hidden
<email@hidden> wrote:
From: email@hidden <email@hidden>
Subject: Re: WOLongResponsePage issues
To: "shravan kumar" <email@hidden>
Cc: email@hidden
Date: Friday, July
24, 2009, 12:30 PM
Hello, Why not using Ajax capabilities of the project Wonder like ajaxprogressbar ? It's easy to implement except dealing with thread and session if you're working with editing context. Jérémy -----webobjects-dev-bounces+jeremy.deroyer=email@hidden a écrit : -----
A : WO Dev Group <email@hidden>
De : shravan kumar
<email@hidden>
Envoyé par : webobjects-dev-bounces+jeremy.deroyer=email@hidden
Date : 24/07/2009 08:54
Objet : WOLongResponsePage issues
Hi Group,
I am having trouble developing a long response page!!! I have developed a page which extends WOLongResponsePage component and implemented performActionI(), ... methods. I have actually referred to SimpleRefreshPage example from WebObjects distribution.
Am not sure what the problem is, but I have various issues:
1) Not able to create
a component in "pageForResult()" method (error says, context is null, ...). So I have created the component in the calling page and passing the created component to long response and returning this component in pageForResult() method. But I have read in WO that, if a component is created and cached in a variable, we have to invoke
ensureAwakeInContext(context) method to make sure the cached component is awakened and is up in the session store.
2) I have placed a flash movie (.swf file) in the long response page, so the movie plays and replays as the page refreshes (this flash movie does not read any value from long response page like: status of long response, ...).
3) Issue: The long response page is NOT refreshing and after some time "No instance available" message is shown in the browser, but note that server is continuing processing my request.
4) Below is the code snippet from my long response page:
Number refreshCount = new Integer(1);
public void appendToResponse(...) {
setRefreshInterval(refreshCount);
super.appendToResponse(...);
}
public Object
performAction() {
Object value = processImages();
//value is of boolean type
return value;
}
/**
User & CImage are EO's and we using session's defaulteditingcontext here.
*/
private boolean processImages() {
User usr = ((Session)session()).loggedInUser();
boolean isSuccess = CImage.processImages(usr);
return isSuccess;
}
public WOComponent pageForResult() {
return nextPage;
}
public WOComponent refreshPageForStatus() {
return this;
}
5) If anyone could advise me do's and don'ts of WOLongResponsePage coding and best practices, that would be great. I see we are really missing nice documentation on WOLongResponsePage usage.
Unfortunately, I cannot user ERXWOLongResponsePage.
Please suggest what am I doing wrong here/ probable solutions.
Thanks in advance,
Shravan Kumar. M
-------------------------------------
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your
_______________________________________________
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
|
|
|