RichTextNavigator.getFirstElement(RichTextItem.RTELEM_TYPE_FILEATTACHMENT) does not get an attachment with DIIOP connection?

Document with 1 richtext item with 2 attachments, external Java program.

RichTextNavigator rtnav = rtItem.createNavigator();

boolean test = rtnav
.findFirstElement(RichTextItem.RTELEM_TYPE_FILEATTACHMENT); //<-This returns true.

EmbeddedObject embObj = (EmbeddedObject) rtnav.getElement();//<- This return null.


embObj = (EmbeddedObject) rtnav.getFirstElement(RichTextItem.RTELEM_TYPE_FILEATTACHMENT);//<- This also return null.

With a local Domino connection everything is fine.

Domino 11.0.1 FP1 Server, Notes Client 11.0.1 FP1


What is wrong with this program?
Or can RichTextNavigator not be used with DIIOP connection?

Hi Thomas,

Seems like RichTextNavigator cannot be used with server having DIIOP enabled.

This was also reported way back via SPR #SODY758JQ9.

It was reported there that -->

RichTextNavigator does not work for attachments.

EmbeddedObject will be null even though the attachment is found.

***********************

I can see below workaround suggested for this SPR.

Use below get to the attachments.

Vector v = rti.getEmbeddedObjects();
Enumeration e = v.elements();
while (e.hasMoreElements()) {
EmbeddedObject eo = (EmbeddedObject)e.nextElement();
System.out.println("\t" + eo.getName());
}

You can consider other methods as well to achieve your requirement.

Regards,

Amit Sharma

Hi Amit,

thanks for your answer. So I have to use a local Notes connection for this (I need the navigator because I want to replace the attachment with a String. Any idea where I can find a list with all SPR's on the HCL site? So I could have a look for myself.

Regards,

Thomas Stüttner

Hi Thomas,
You can refer to below URL -->


https://ds_infolib.hcltechsw.com/ldd/fixlist.nsf

Regards,
Amit Sharma

Hi Amit,

thanks again. But this was not what I look for. For example the SPR #SODY758JQ9 you mentioned is not in this list, because it is not fixed.

Hi Thomas,

There are multiple SPR created for "n" number of issues.

The development team picks SPR depending upon the weightage every SPR has, the impact it created and many other conditions.

The URL shared by me will display the SPR that has been fixed and were raised in different releases of Domino/Notes.

It seems that SPR SODY758JQ9 doesnot meet the valid criteria yet (such as enough weightage,count of number of issues reported etc.) and hence it doesnot appear in the URL shared by me.

Regards,

Amit Sharma