Skip to Content
author's profile photo Former Member
Former Member

Any order in execution of same-page iViews?

Hello, colleagues,

Is it possible to garantee in some way order of execution of portal components on the same page?

Let's say we have two (non-isolated, to have more chance to make it work) iViews A and B on the same page of EP6. The iView A does some job on the server-side and saves the result in the session, and the iView B uses that result for its own rendering. Is there a way to guarantee that A will finish the job before B reads the result in the session? For example, are doProcessAfterInput() methods of all iViews processing the same request executed before doProcessBeforeOutput() method of any single iView?

My guess is that the answer is No, but would like to verify it with Portal guys 😊 Is there a recommended solution? If I use client-side eventing to transfer data from A to B, that means that B will have to be re-loaded to transfer to its server-side processor the data from A. I would like to avoid it.

Thanks for your help,

Arman

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Nov 25, 2003 at 02:55 PM

    There is a possibility to influence the dispatcher . It s documented in the PRTGuide here in SDN EP. (e.g. Hooks). But I do not recommend to do so.

    There several other possibilities. EPCF: yes. Also Portal Object Model can be used.

    Oliver

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.