You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsrp4j-user@portals.apache.org by Venkatesan Krishnamoorthy <ve...@infosys.com> on 2006/04/12 18:18:23 UTC

Optimizing performBlockingInteraction

Hi:

I want to know if there is a configurable way of enabling markup string response as part of the performBlockingInteraction operation response in WSRP4J. The WSRP primer says that  a WSRP producer can optionally choose to return the markup string in response to the performBlockingInteraction method call rather than to wait for another call to getMarkup method to return the markup string. I tweaked the performBlockingInteraction code in WSRPEngine.java as follows to achieve the same. But I would like to know if there is any configurable way to achieve this w/o modifying the code. Please let me know.



public class WSRPEngine implements

   oasis.names.tc.wsrp.v1.intf.WSRP_v1_PortletManagement_PortType,

   oasis.names.tc.wsrp.v1.intf.WSRP_v1_Markup_PortType,

   oasis.names.tc.wsrp.v1.intf.WSRP_v1_Registration_PortType,

   oasis.names.tc.wsrp.v1.intf.WSRP_v1_ServiceDescription_PortType {

   public BlockingInteractionResponse performBlockingInteraction(

                                                                                                PerformBlockingInteraction request)

   throws RemoteException {

      ...

      ...

      return invokeGetMarkup(request, interactionResponse);

   }

// Optimization to return markup string as part of performBlockingInteraction operation response

// Refer to section 5.2.2 of the WSRP primer published on the site

// http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html#REF6

   private BlockingInteractionResponse invokeGetMarkup(PerformBlockingInteraction request,

                                                                                    BlockingInteractionResponse interactionResponse)

   throws RemoteException {

      GetMarkup markUpRequest = new GetMarkup();

      markUpRequest.setMarkupParams(request.getMarkupParams());

      markUpRequest.getMarkupParams().setNavigationalState(interactionResponse.getUpdateResponse().getNavigationalState());

      markUpRequest.setPortletContext(request.getPortletContext());

      markUpRequest.setRegistrationContext(request.getRegistrationContext());

      markUpRequest.setRuntimeContext(request.getRuntimeContext());

      markUpRequest.setUserContext(request.getUserContext());

      MarkupResponse markUpResponse = getMarkup(markUpRequest);

     interactionResponse.getUpdateResponse().setMarkupContext(markUpResponse.getMarkupContext());

     return interactionResponse;

  }

  ...

  ...

}




**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***