LO59404: RICHTEXTOPTION NOT IMPLEMENTED IN EXPORTDXL

APAR status

• Closed as fixed if next.

Error description

• ENV:
  I reproduce the issue on Domino 8.5.1/8.5.2 on windows, 8.5.2 on
  Linux.
  
  From the Designer help, RichTextOption is defined in
  DxlExporter. and there are
  two methods: getRichTextOption and setRichTextOption:
  
  Read-write. Specifies the format of richtext items that occur in
  the exported
  DXL.
  Note  This property is new with Release 8.
  Defined in
  DxlExporter
  Data type
  int
  Syntax
  public int getRichTextOption()    throws NotesException
  public void setRichTextOption(int option)    throws
  NotesException
  Legal Values
  RICHTEXTOPTION_DXL (0) (default) Richtext is output in its
  normal DXL format,
  as a <richtext> element.
  RICHTEXTOPTION_RAW (1) Richtext is output as a <rawitemdata>
  element containing
  the raw data for the richtext item, encoded in Base64.  This
  option can be
  useful if the only purpose of the DXL will be to import it into
  another
  database, because it assures that the imported data will be
  precisely the same
  as the original.
  
  But when the two methods are called, it will It will failed on
  the following
  two lines:
  // System.out.println("richtextoption
  "+exporter.getRichTextOption());
  // exporter.setRichTextOption(1);
  
  Error message:
  
  NotesException: Not implemented
          at lotus.domino.cso.Base.notImplemented(Unknown
  Source)
          at
  lotus.domino.cso.DxlExporter.setRichTextOption(Unknown Source)
          at
  com.tsmc.emd.main.DiiopToXml.main(DiiopToXml.java:43)
  Unexpected exception:null
  
  Screen shot of the error message:
  
  
  
  
  Here is the sample standalone Java application. It will failed
  on the following
  two lines:
  // System.out.println("richtextoption
  "+exporter.getRichTextOption());
  // exporter.setRichTextOption(1);
  
  If the two lines above are removed, the Java application run
  without problem.
  
  
  Steps:
  Note: please change server IP address, user name and password as
  needed.
  1. load diiop on Domino server
  2. open a terminal window
  3. issue the command:
  set CLASSPATH=.;c:\notes\data\domino\java\NCSO.jar
  javac DiiopToXml.java
  4. issue the command to run the application:
    java DiiopToXml
  
  
  But if I call the methods in Java Agent, it will run without
  error.
  Here is the java agent. You can find the agent named 'Hello' in
  DXL1.nsf
  uploaded in attachment db.
  import lotus.domino.*;
  
  public class JavaAgent extends AgentBase {
  
      public void NotesMain() {
  
        try {
  
            // (Your code goes here)
  
         Session session = getSession();
          AgentContext agentContext = session.getAgentContext();
  
  
          // Get current database
          Database db = agentContext.getCurrentDatabase();
          DocumentCollection v = db.getAllDocuments();
          Document doc = v.getFirstDocument();
  
          // Export to file
          System.out.println("begin");
          String filename = "JavaExported.dxl";
          Stream stream = session.createStream();
          if (stream.open(filename)) {
            stream.truncate(); // Any existing file is erased
            DxlExporter exporter = session.createDxlExporter();
            System.out.println("RichTextOption "+
  exporter.getRichTextOption());
        exporter.setRichTextOption(1);
        System.out.println("RichTextOption "+
  exporter.getRichTextOption());
            System.out.println("Exported " +
               stream.writeText(exporter.exportDxl(doc)) +
              " bytes to " + filename);
          }
          else
            System.out.println("Cannot open " + filename);
        } catch(Exception e) {
            e.printStackTrace();
         }
     }
  }
  
  Steps:
  1. copy DXL1.nsf to your server
  2. sign with your own ID
  3. tell amgr run DXL1.nsf 'Hello'
  
  Note:
  However, in the Java Agent, exporter.setRichTextOption(0) and
  exporter.setRichTextOption(1) made no difference.
  The exported DXL is always in raw data format.
  

Local fix

• N/A
  

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# XYGU8F7CV4.
  The problem will be fixed in a future release if there is one.
  

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

• R852 PSN

     UP