Forum Stats

  • 3,852,434 Users
  • 2,264,103 Discussions
  • 7,905,063 Comments

Discussions

IPC between WSRP portlets with Desktop Async mode = Compability , WLP 10.0

650542
650542 Member Posts: 13
edited Aug 4, 2008 4:54AM in WebLogic Portal
Hi all,

Is it possilble to do IPC between remote portlets when the desktop async update mode = Compability (portlet level) ? Speak another way, how to pass some values from portlet A (submit a form, click on a link) to portlet B when they are placed on consumer portal and the async mode = Compability (only the portlet A is updated, the portal page is not reload => Event handler or passing via URL doesn't work because code of portlet B is not invoked at all).

I tried to fire a custom event when submit a form on portlet A and expect that portlet B would react to that event (using PortletBackingContext.fireCustomEvent)
That works fine when portlet A, and B are on local portal, but the event is not sent to portlet B when they are placed on consumer portal with desktop = compability mode. When the consumer desktop is change to async mode = Enable then portlet B received the event fired by portlet A but the outerRequest.getAttribute() received null. So passing value between A and B is not possible.

Comments

  • 653105
    653105 Member Posts: 7
    Is it possilble to do IPC between remote portlets when the desktop async update mode = Compability (portlet level) ?
    No you must have desktop async set to one of the other two (enabled, disabled)

    If you still want AJAX functionality try using "enabled" this will still give you portlet level AJAX and update only the portlets that have changed.
  • 650542
    650542 Member Posts: 13
    It is not so clear for me what exactly portlet level ajax mode is. Let say if you put 2 portlets A and B on the pages, when you click on a link on portlet A which is point to an action:
    - If the mode is "compability": then only portlet A action is called and if the action update or generate new content, it will be updated for portlet A, the portal page is not reload, only the div that contain portlet A is updated.
    - Similar scenario, what would happen if "enable" mode is used? The portal page is reload? the refresh action of portlet B is also called? or only the current jsp of portlet B is called?
This discussion has been closed.