Ajax requests and lifecycle mapping

At last week's JSR286 EG F2F, two proposals for processing fragment 
requests were discussed.

The first one is based on what we have discussed in the WSRP TC so far, 
i.e mapping of blockingAction URLs to pbia, and render URLs to 
getMarkup. In both these cases, the data/markup fragment generated by 
the producer is meant for consumption by the portlet on the user-agent.

The second one is a mapping of *all* fragment requests to pbia, 
effectively disregarding the type of the URL.

It was argued that the second one provides a simpler API for portlet 
developers as well developers of portlet bridges.

I took a quick stab at mapping the second proposal to the WSRP 
lifecycle. Please find it attached.

Subbu
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.