Displayed here is a section of our internal log, showcasing the compositeData for 2 distinct custom controls - one being the caller and the other being the callee. This information is captured during the BeforePageLoad event.
The parameter dataSource is passed "as-is", utilizing
dataSource="#{javascript:compositeData.dataSource}
Log Entries
14:37:29.876 {dataSource=com.ibm.xsp.model.domino.wrapped.DominoDocument@379c379c, dataSource2=com.ibm.xsp.model.domino.wrapped.DominoDocument@379c379c}
14:37:29.894 {dataSource=com.ibm.xsp.binding.javascript.JavaScriptValueBinding@31433143, dataSource2=com.ibm.xsp.binding.javascript.JavaScriptValueBinding@32613261}
In the second custom control (invoked by the first), the dataSource experiences an unexpected transformation, rendering it essentially useless.
Inquiry
How could a binding alter its type suddenly, switching from a wrapped DominoDocument to a JavaScriptValueBinding? Furthermore, what steps can be taken to rectify this situation?
PS: dataSource2 was an attempt to transmit a secondary parameter all the way down from the top, linked to the same wrapped NotesDocument.
Temporary Solution
To address the issue of passing the document through a parameter, I have resorted to using the original NotesDocument as specified on the main page. While this serves as a quick fix enabling us to proceed, there remains a desire for clarification regarding this anomaly (whether originating from XPages or my implementation) and guidance on the proper method for handling parameter transmission.