Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-25086

SOAP renderContent needs to support storage format content

    XMLWordPrintable

Details

    Description

      Current support assumes the content is wiki and there is no option for storage format. This must have been missed when 4.0 was done. Need option for either wiki or storage format. Need to leave the wiki option as default so it doesn't cause a compatibility problem.

      Suggest adding an option in the extended service API that has the parameters parameter: String renderContent(String token, String spaceKey, String pageId, String content, Hashtable parameters). Something like this:

      PagesSoapService
      public String renderContent(String spaceKey, long pageId, String newContent, Map parameters) throws RemoteException
    {
        ...
        if (StringUtils.isNotBlank(newContent))
        {
            String renderedContent;
            if ((parameters.containsKey("format") && "storage".equalsIgnoreCase((String parameters.get("format")) {
                renderedContent = renderContent(page.getSpaceKey(), page.getId(), newContent); 
            } else { 
                renderedContent = wikiStyleRenderer.convertWikiToXHtml(pageContext, newContent);
            }
        }
        ...

      Attachments

        Issue Links

          derived from

          Suggestion - CONFSERVER-36424 REST API to render content needs content id support

          • Closed

          Activity

            People

              Unassigned Unassigned
              bob.swift@charter.net Bob Swift OSS (Bob Swift Atlassian Apps)
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: