[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [wsrp-wsia] [I#122] Mismatch with JSR168 definition of Action (JSR168)
Status: Active Topic: Interface Class: Technical Raised by: Alejandro Abdelnur Date Added: 30-Oct-2002 Title: Mismatch with JSR168 definition of Action (JSR168) Description: Action definition differs between JSR168 and WSRP. WSRP defines actions as the event where all state changes happen. JSR168 defines actions as the event where state changes that affect other portlet changes happen. When JSR168 EG decided to get rid of non-blocking action from the API one of the key arguments was that it could still be possible to model non-blocking actions by using getMarkup. This non-blocking behavior can and should only be used if the portlet is not modifying a state that may affect other portlets, otherwise the overall behavior may not be deterministic. This means a different programming model for WSRP and JSR portlets. Specifically, JSR168 allows changing properties in getMarkup. WSRP does not allow changing properties during the getMarkup. Impact: Medium/High. JSR168 based producers would have to use producer managed properties. Providing that WSRP remove this restriction in the case of producer managed properties. Or, as part of the WSRP programming guidelines it would have to have extra requirements for JSR168 portlet developers.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC