LO80498: XPAGE: MULTIPLE BODY MAKES MULTIPLE MULTIPARTS

APAR status

• Closed as fixed if next.

Error description

• Customer is using Xpage application that has two Rich Text
  controls (they bind different body fields).
  
  When user insert an image or upload a file to the second Rich
  Text controls, duplicate "multipart/related" or
  "multipart/mixed" are created in the second Rich Text Field.
  And user edit to insert an image after saving the document with
  inserted image or uploaded file, "multipart/related" is
  increased.
  And user edit to upload a file after saving the document with
  inserted image or uploaded file, "multipart/mixed" is increased.
  
  This issue is reproduced only when application has two Rich Text
  controls.
  "multipart/related" or "multipart/mixed" are increased on the
  second Rich Text Field.
  
  Steps to reproduce:
  1. Create a Form, and create two Rich Text Field (Body and
  Body_1)
  2. Create a Xpage
  3. Put two Rich Text controls and bind them to different Rich
  Text Field each
  4. Put two Upload and Download controls and bind them to
  different Rich Text Field each
  5. Create a new document via Xpage
  6. "multipart/related" or "multipart/mixed" are increased as the
  following
  
  ---- Insert a image to the both field and save it
  Body
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR9671UHRUHIHD"
  
  Body_1
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR38025UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR38025UHRUHIHD"
  
  Body_1 has duplicate "multipart/related" <--- problem
  
  ---- upload a file to the both field and save it
  Body
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR899UHRUHIHD"
  
  Body_1
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR23263UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR23263UHRUHIHD"
  
  Body_1 has duplicate "multipart/mixed" <--- problem
  
  ---- insert a image on the second Body_1 and save it -> upload a
  file on the second Body_1
  Body_1
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR48017UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR48017UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR51236UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR51236UHRUHIHD"
  
  "multipart/related" or "multipart/mixed" are increased <---
  problem
  
  ---- insert image on the second Body_1 and save it -> delete
  image and upload file -> insert image
  Body_1
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR44108UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR44108UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR44108UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR16305UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR16305UHRUHIHD"
  
  "multipart/related" or "multipart/mixed" are increased <---
  problem
  
  ---- upload file on the second Body_1 and save it -> delete file
  -> insert image -> upload file
  Body_1
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR11706UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR11706UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR34285UHRUHIHD"
  
  Content-Type: multipart/related;
   boundary="==IFJRGLKFGIR34285UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR65024UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR65024UHRUHIHD"
  
  Content-Type: multipart/mixed;
   boundary="==IFJRGLKFGIR65024UHRUHIHD"
  
  "multipart/related" or "multipart/mixed" are increased <---
  problem
  

Local fix

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# MNAA9KDAUX.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels