Uploaded image for project: 'Chemistry (Retired)'
  1. Chemistry (Retired)
  2. CMIS-974

Parsing Exception: Extensions tree too wide

    XMLWordPrintableJSON

Details

    • Important

    Description

      When using opencmis to get object by path from alfresco, it will report exception:

      parsing exception: Extensions tree too wide!.

      The method I use to create document is as follow:

      /**

      • Returns a CMIS object from the session cache. If the object is not in the
      • cache or the cache is turned off per default {@link OperationContext}

        , it

      • will load the object from the repository and puts it into the cache.
      • <p>
      • This method might return a stale object if the object has been found in
      • the cache and has been changed in or removed from the repository. Use
      • {@link CmisObject#refresh()}

        and

        {@link CmisObject#refreshIfOld(long)}

        to

      • update the object if necessary.
      • @param path
      • the object path
      • @return the requested object
      • @throws CmisObjectNotFoundException
      • if an object with the given ID doesn't exist
      • @cmis 1.0
        */
        CmisObject getObjectByPath(String path);

      It happens when there are many tags added for a specific folder, the API and the workbench will both report the same error.

      The url I use to connect to the repository of alfresco is:
      http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/atom
      Now I have to use
      http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/browser
      to make it work.

      I found there are limitation set for extensions tree width, the same code works find when using browser binding repository url.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nettree Zhi Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

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