Problem while integrating exo Remote Portlets on WPS

[adrien.geymond@xxxxxxxxxxxx]

Hello all,

I am trying to work on the "exo portlet container" in order to deploy some 
remote portlets on a Webspere portal (WPS) using exo WSRP container.

That is the reason why I have downloaded the exoPC-1.5-tomcat.zip. I have 
unzipped this package and started tomcat without any new configuration.

I have some problems while i am trying to access my own portlet and Exo 
sample portlets (UTF8 Portlet for instance).

I have made some investigations using the code coming from the SVN 
repository. You will find below results of my investigation :

   1/ I am unable to display any exo remote portlet due to a null 
pointerException. 
     
******************************************************************************
    => To avoid this Null Pointer Exception, i need to update the value 
wsrp.does.url.template.processing in the class  
org.exoplatform.services.wsrp.producer.impl.WSRPConfiguration.java to false.
    Else i have a Null Pointer Exception in method getMarkup(157) of the 
class MarkupOperationsInterfaceImpl because there is no tag template in the 
runtimeContext of the SOAP Message coming from WPS.

Here is a sample SOAP Message caught by TCPMonitor:

POST /wsrp/services/WSRPBaseService HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: IBM WebServices/1.0
Host: localhost:8081
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "urn:oasis:names:tc:wsrp:v1:getMarkup"
Content-Length: 1297

<?xml version="1.0" encoding="utf-8"?>
   <soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
      <soapenv:Header/>
      <soapenv:Body>
         <getMarkup xmlns="urn:oasis:names:tc:wsrp:v1:types">
            <registrationContext>
               
<registrationHandle>5dce3dc6c0a80c7300c8ccb168f98eba</registrationHandle>
            </registrationContext>
            <portletContext>
               <portletHandle>portlets/Utf8Portlet</portletHandle>
            </portletContext>
            <runtimeContext>
               <userAuthentication>wsrp:none</userAuthentication>
               <portletInstanceKey>7_0_1C9</portletInstanceKey>
               <namespacePrefix>wsrp_rewrite_</namespacePrefix>
            </runtimeContext>
            <userContext>
               <userContextKey>admin</userContextKey>
               <profile/>
            </userContext>
            <markupParams>
               <secureClientCommunication>0</secureClientCommunication>
               <locales>fr</locales>
               <locales>en</locales>
               <mimeTypes>text/html</mimeTypes>
               <mode>wsrp:view</mode>
               <windowState>wsrp:normal</windowState>
               <clientData>
                  <userAgent>Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; 
rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1</userAgent>
               </clientData>
               <markupCharacterSets>UTF-8</markupCharacterSets>
               <validNewModes>wsrp:view</validNewModes>
            </markupParams>
         </getMarkup>
      </soapenv:Body>
   </soapenv:Envelope>

    2/ Problem with Consumer URL rewriting. 
     **************************************
 The consequence of this change is that we have to produce URL using a 
different way. For instance, we use ConsumerRewriterPortletURLImp class to 
produce URL.
I think that there is a bug while generating URLs ( maybe i am wrong, but i 
do not find the right configuration). Actually, it seems to me that urls are 
not well encoded because we are not able to have the appropriate behavior for 
any links or form.
Hereafter some information while trying to display the UTF8Portlet :

Here is the markupString tag in the SOAP response from Exo Tomcat :
 
<markupString>text: --&lt;p&gt;form:&lt;form 
action=&quot;wsrp_rewrite?&amp;wsrp-urlType=text/html&amp;wsrp-portletHandle=portlets/Utf8Portlet/windowID&amp;wsrp-navigationalState=726a1cfec0a80c73014d659d06c98b25&amp;wsrp-sessionID=726a1c90c0a80c73006545d2824f6274&amp;wsrp-secureURL=false/wsrp_rewrite&quot;
 method=&quot;post&quot; 
enctype=&quot;application/x-www-form-urlencoded&quot;&gt;&lt;input 
type=&quot;text&quot; 
name=&quot;text&quot;/&gt;&lt;/form&gt;&lt;/p&gt;&lt;p&gt;&lt;a 
href=&quot;wsrp_rewrite?&amp;wsrp-urlType=text/html&amp;wsrp-portletHandle=portlets/Utf8Portlet/windowID&amp;wsrp-navigationalState=726a1cfec0a80c730144752d784a023d&amp;wsrp-sessionID=726a1c90c0a80c73006545d2824f6274&amp;wsrp-secureURL=false/wsrp_rewrite&amp;amp;text=%F2%E5%F1%F2&quot;&gt;link&lt;/a&gt;&lt;/p&gt;</markupString>

Here is the link as it appears in HTML content produce by WPS :
<p><a 
href="wsrp_rewrite?&wsrp-urlType=text/html&wsrp-portletHandle=portlets/Utf8Portlet/windowID&wsrp-navigationalState=726a1cfec0a80c730144752d784a023d&wsrp-sessionID=726a1c90c0a80c73006545d2824f6274&wsrp-secureURL=false/wsrp_rewrite&amp;text=%F2%E5%F1%F2">link</a></p>

As you can see, it can not work with a link like that.

Do you have any idea or work around to move forward with the integration of 
EXO Remote portlets in WPS.

For your information, i have deployed sucessfully the same portlet on WPS 
using an other wsrp framework. So the problem does not come from WPS.

We really want to implement our portlets with EXO framework for this customer 
... so i hope that somebody could help us.

Do not hesitate to contact me if you need more information.

Kind regards,

Adrien Geymond