MarkupParams reuse in pbia()

[Richard Jacob <richard.jacob@de.ibm.com>]

Hi all,

I have a received some comments from developers concerning actions and mode
window state passing.
There is a feel that the current definiton of pbia() and the MarkupParams
contained therein are not cleanly described.
- MarkupParams are not optional, but we (a little bit fuzzy) state that in
6.1.11 (spec 1.0) that MarkupParams are for markup generation. In the case
of pbia() this refers to the optimization.
- windowsState and Mode are not optional and needed for pbia(). But we
don't say in the spec that the passed mode and window state is really the
current mode/state in which the action is invoked().
If optimizaton is used for pbia() to retrieve markup, how can mode/state be
"passed" to the follow on render request on the producer side? Do these
have (implicitly) to be the same? Is a switch of these between the phases
not possible?
Without the optimization it is.

So it seems we are quite fuzzy here and the question here is whether we
should be more explicit on the structure usages for the two phases.

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Team Lead & Technical Lead
WSRP Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com