Bug 908853 - WSRP export data returns a different portletHandle from the one provided during the export.
Summary: WSRP export data returns a different portletHandle from the one provided duri...
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.2.1.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-07 16:51 UTC by Gary Hu
Modified: 2020-04-27 01:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPC-101 0 Major Resolved When importing a portlet, the portlet id used for the associated state should refer to the original portlet 2013-04-09 11:12:36 UTC
Red Hat Issue Tracker GTNWSRP-349 0 Major Resolved When exporting a portlet, the returned portlet handle should be the same as the one provided during the export 2013-03-28 11:58:24 UTC

Description Gary Hu 2013-02-07 16:51:01 UTC
After making WSRP export request, the response data includes a portletHandler that is different from the one provided.

For example:

REQUEST:
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
 <env:Header xmlns:work='http://bea.com/2004/06/soap/workarea/'>
  ...
 </env:Header>
 <env:Body>
  <v2:exportPortlets xmlns:v2='urn:oasis:names:tc:wsrp:v2:types'>
   <v2:registrationContext xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:nil='true'/>
   <v2:portletContext>
    <v2:portletHandle>Original_PortletHandle</v2:portletHandle>
   </v2:portletContext>
   <v2:userContext xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:nil='true'/>
   <v2:lifetime xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:nil='true'/>
   <v2:exportByValueRequired>1</v2:exportByValueRequired>
  </v2:exportPortlets>
 </env:Body>
</env:Envelope>


RESPONSE:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <exportPortletsResponse xmlns="urn:oasis:names:tc:wsrp:v2:types">
         <exportContext>rO0ABXcWAAdXU1JQX0VDP/AAAAAAAABFTVBUWQ==</exportContext>
         <exportedPortlet portletHandle="A_Different_PortletHandle_From_Original_One">
            <exportData>xxxx</exportData>
         </exportedPortlet>
      </exportPortletsResponse>
   </env:Body>
</env:Envelope>

Comment 1 JBoss JIRA Server 2013-03-28 11:58:24 UTC
Chris Laprun <chris.laprun> updated the status of jira GTNWSRP-349 to Resolved

Comment 2 JBoss JIRA Server 2013-04-09 11:12:36 UTC
Chris Laprun <chris.laprun> updated the status of jira GTNPC-101 to Resolved

Comment 3 JBoss JIRA Server 2013-04-09 11:12:36 UTC
Chris Laprun <chris.laprun> made a comment on jira GTNPC-101

Fixed by https://github.com/gatein/gatein-pc/pull/4

Comment 4 JBoss JIRA Server 2013-04-09 11:16:32 UTC
Chris Laprun <chris.laprun> made a comment on jira GTNPC-101

Fixed by https://github.com/gatein/gatein-pc/pull/4 and https://github.com/gatein/gatein-pc/commit/710b1aa9d3cab758252b31b4317d706f64cd3826


Note You need to log in before you can comment on or make changes to this bug.