• Name Picker

    By Neil J McMillan 1 decade ago

    Server page persistence set to 'Keep pages in memory' or 'Keep only current page in memory'

    Only happens on saved documents, OK on new documents.

    Document is loaded using opendominodocument.xsp in the url

    Click on the name picker control and I get the following error at the server console (also get a dialog error in the browser)

    HTTP JVM: com.ibm.xsp.webapp.FacesServlet$ExtendedServletException: com.ibm.xsp.FacesExceptionEx: Unable to get document page name for null

    When I click OK on the dialog error, the name picker loads but contains no data from the public address book

    Works fine if Server page persistence set to 'Keep pages on disk'

     

    • Do you have a sample?

      By Philippe Riand 1 decade ago

      Please send me a db, with the steps to reproduce. Else, it is too hard to reproduce.

    • Me too Same Setup Same behavior <EOM>

      By Michael Strong 1 decade ago
    • Same at me

      By Sascha Meier 1 decade ago

      I can confirm this behavior. Same problem in my Application!

      • Can you please isolate some sample code for me?

        By Philippe Riand 1 decade ago
        • Sorry for the delay...

          By Sascha Meier2 1 decade ago

          For explanation:

          We have the NamePicker control inside a tabbed panel control. it is working correctly if the application settings are set to keep pages on disk. in every other setting there is the error 500.

          In the same xpage we have also a dialog. within this dialog the NamePicker control is working correctly.

          Piece of code for NamePicker:

                                                              for="hiddenVA_Quali01">
                                      
                                                                               viewName="($LookupPersonal)" label="$25">
                                               return adr}]]>
                                          
                                      

                                      
                                      
                                                                               value="10000">
                                          

                                      

                                      
                                  

    • Same Problem

      By Alex James Woodall 1 decade ago

       

      I'm having the same problem:

       

      &lt;xp:inputText id=&quot;AddRecipientNamePickerField&quot;&gt;
      
      &lt;/xp:inputText&gt;
      
      &lt;xe:namePicker id=&quot;AddRecipientNamePicker&quot;
      
      for=&quot;AddRecipientNamePickerField&quot; dialogTitle=&quot;Add a Recipient&quot;&gt;
      
      &lt;xe:this.dataProvider&gt;
      
      &lt;xe:dominoNABNamePicker addressBookDb=&quot;names.nsf&quot;
      
      groups=&quot;false&quot;&gt;
      
      &lt;/xe:dominoNABNamePicker&gt;
      
      &lt;/xe:this.dataProvider&gt;
      
      &lt;/xe:namePicker&gt;
      

      Works fine via

      ER.xsp?documentId=68701E22E99A616480257B2F00349160

      but not via

      $$OpenDominoDocument.xsp?documentId=68701E22E99A616480257B2F00349160

      And in the log.nsf I get

      15/03/2013 11:37:03   HTTP JVM: com.ibm.xsp.webapp.FacesServlet$ExtendedServletException: com.ibm.xsp.FacesExceptionEx: Unable to get document page name for null

       

      Has anyone found a fix for this? Passing the "xpage to open" from the view isn't ideal as I'm using the Dynamic View control inside my own control that's inherited from my standard base design into multiple applications that have different xpage names etc.

       

      Seems to be the same as per here: http://www.openntf.org/internal/home.nsf/defect.xsp?action=openDocument&documentId=604492C39CCA196186257B0B000DE7AE