Accessing OPS page flow urls through an ajax request...

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Accessing OPS page flow urls through an ajax request...

Vikas Sasidharan

Hi,

 

My current project involves a UI which is very similar to that of a typical mail client (Outlook, Thunderbird etc.). In other words, our screen is split into a “list pane” (upper half) and a “preview pane” (bottom half) where each pane is actually just an HTML div. Whenever the user selects one of the items in the list pane, we have to asynchronously retrieve the summary data for that item and display it in the preview pane.

 

In this architecture, we are using OPS for rendering the preview data only. Everything else, including the ajax request made by the upper pane, is implemented using Dojo (http://dojotoolkit.org/). So, a typical scenario runs like this:

 

1)       User selects an element in the list pane.

2)       The selection event triggers Dojo to make an ajax call to a WebWork action.

3)       The action forwards to an OPS page flow url.

4)       The html+css+js content that is generated by OPS for the above page flow is sent back to the client as the ajax response.

5)       Dojo parses the received html content. In this process it does the following:

a.       Picks up all the <style …> and <script …> tags found in the response and moves them to the top of the containing page.

b.       Picks up the contents of the <body> tag and inserts them into the “preview pane” div.

 

Note: Steps (a) and (b) are needed because the response itself is a complete HTML page and cannot hence be directly included within another (parent) html page.

 

Now that the story is over, here is the crib ;-). With this in place, we are seeing that the preview pane is getting rendered fine but none of the javascripts are working. So, for example, I am able to see a calendar control but on clicking it nothing happens (not even any errors). Just to make sure that this is not a Dojo issue, we even hard coded all the ops styles and javascripts in the parent document. Still no luck!

 

My assumption is that OPS relies on “window.onload” events for proper initialization of its javascripts and hence without them being called, things are going south. Am I right by any chance?

 

This issue is really haunting us, so any help/suggestions would really be appreciated.

 

Thx & Rgds,

Vikas

 

"Quidquid latine dictum sit, altum sonatur"
Whatever is said in Latin, sounds profound

 



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws