Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-3884

Email Document sometimes loses DocumentManager

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.2 GA
    • Fix Version/s: 5.3 RC
    • Component/s: None

      Description

      Intermittently the emailDocument page breaks, during the AJAX search for User. When the search result returns the NavigationTree sometimes becomes empty. The log at this point has:

      10:13:19,807 WARN [TreeActionsBean] Could not initialize the navigation tree: no parent found for current document
      10:13:19,904 ERROR [NavigationContextBean] <resetCurrentPath> documentManager not initialized
      10:13:19,917 WARN [TreeActionsBean] Could not initialize the navigation tree: no parent found for current document
      10:13:20,018 ERROR [NavigationContextBean] <resetCurrentPath> documentManager not initialized

      If you then try to continue and send the email you are returned to the emailDocument form with empty fields, NavigationTree and document title. In the log you have a stacktrace (snippet below) and the email is not sent.

      10:16:34,829 ERROR [DefaultActionFilter] evaluation of condition SeamContext.get("isInsidePersonalWorkspace") failed: returning false
      org.jboss.seam.RequiredException: @In attribute requires non-null value: userWorkspaceManagerActions.documentManager
      at org.jboss.seam.Component.getValueToInject(Component.java:2264)
      at org.jboss.seam.Component.injectAttributes(Component.java:1687)
      at org.jboss.seam.Component.inject(Component.java:1505)

      From my brief debugging it appears that the ServerLocation is shomehow lost - from the code comments, a situation already seen at times? In this case, something to do with the conversation ID not being propagated in the ajax request maybe? Should/why would the NavigationTree be an a4j refresh region?

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 4 hours
                4h
                Logged:
                Time Spent - Not Specified
                Not Specified