exportPortlets semantics for portlets with opaque portletState

[Subbu Allamaraju <subbu@bea.com>]

What are the semantics of exportPortlets of portlets having opaque state 
(i.e. portletState)?

The current language in the spec for import/export does not exclude 
producers using portletState to carry a partial/full representation of 
state of portlets. However, the signature of exportPortlets does.

Let's say there are two portlets with the same handle but with different 
portletState elements. The consumer can send them both within an 
exportPortlets message by sending two portletContenxt elements.

  <exportPortlets>
    <portletContext>
      <portletHandle>A</portletHandle>
      <portletState>Blah</portletState>
    <portletContext>
      <portletHandle>A</portletHandle>
      <portletState>Hah</portletState>
    </portletContext>
    </portletContext>
  </exportPortles>


In response, let's say, the producer returns two

  <exportPortletResponse>
    <exportContext>...</exportContext>
    <exportedPortlets>
      <portletHandle>A</portletHandle>
      <exportData>BlahBlah<exportData>
    </exportedPortlets>
    <exportedPortlets>
      <portletHandle>A</portletHandle>
      <exportData>HahHah<exportData>
    </exportedPortlets>
  </exportPortletResponse>

 From this response, the Consumer has no way to tell which 
exportedPortlets corresponds to which portletContext.

Any comments?

Subbu
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.