Forgot about 2.2 but don't you have a "height" tag in -object.xml ?
I implicitly thought you were talking about ordering the windows to order them in the layout.
If you were really talking about processing (or computing), no you cannot give an order, you should not depend on the ordering. Each window could in theory could be rendered in parallel.
thanks about your quick reply.
so, if i can´t set the processing order, how can i take influence on the ordering/sorting in the database (e.g. via the name of the window (aaaWindow has a lower id than zzzWindow), the length of the name, etc.)?
unfortunately for our application it is very important, that the windows/portlets are processed in a specific order
What if we change the engine to have parallel rendering ? Then the ordering would be totally random.
It's a possibility open by the JSR-168 spec.
Look at "PLT.5.2.4 Request Handling"
The render requests may be executed sequentially or in parallel without any guaranteed order.
Your app must not depend on the ordering of the windows. The only guarantee you have is that the action phase of the triggered portlet will be called before any rendering.
Since all the render phases shouldn't have side-effect, it shouldn't be a problem.
i know that our solution is not 100% clean - but now we need some workaround concerning the processing order until we can fix the problem
activating very old thread. I don't think this might have changed as per spec
but I have a redirect in one of the portlets and i don't want other portlets to process at all.
How can I influence that ?
Right now, even though I am redirecting in one portlet, the other portlet is still invoked.
I want to depend on the order here and How do I restrict this ? any suggestions ?