Re: [wsrp-comment] Public Comment

[Michael Freedman <michael.freedman@oracle.com>]

Though its true the committee hasn't formally considered Ajax support 
for WSRP, we have noted that many Ajax use cases can already be 
implemented using the wsrp resource mechanism. Because wsrp 1.0 limits 
resource access to http your implementation is limited by not having 
access to portlet state, however much can still be accomplished. WSRP 
2.0 removes this restriction yet because the communication is still 
within the the resource mechanism, prevents you from modifying portlet 
state. Removing this last restriction (and subtleties related to 
resources) is a high priority item for us in moving the standard forward.
-Mike-

comment-form@oasis-open.org wrote:

>Comment from: talig@mercury.co.il
>
>Name:Tali
>Title:developer
>Organization:Mercury Interactive
>Regarding Specification:v1 & v2
>
>Hi,
>
>In Mercury we have a portal with WSRP support based on WSRP4J.
>
>I got the task of making it conformant to other WSRP consumers.
>
>I had a real bad experience, because the portals implementations were very buggy.
>
>The most problematic area, in my view , is Ajax support.
>
>There is no way to support Ajax, and if I understand correctly , v2 does not change it.
>
>I think this may be a mistake, in the last year there is a rising demand for Ajax.
>
>I know that JSF v2 will provide support for Ajax related issues - iframes.
>
>It doesn’t seem valid that in WSRP we will be restricted to very simple portlets.
>
>A full page refresh is problematic in case there are heavy WSRP portlets on the page.
>
>An Ajax enhancement would make a much pleasanter user experience.
>
>Tali
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: wsrp-comment-unsubscribe@lists.oasis-open.org
>For additional commands, e-mail: wsrp-comment-help@lists.oasis-open.org
>
>  
>