Uploaded image for project: 'exo-ecms'
  1. exo-ecms
  2. ECMS-2688

LifecycleConnector json response broken with special chars

    Details

    • Similar issues:
      Show 10 results 
    • BV:
      95
    • Support Status:
      Fixed in Product
    • BO:
      0

      Description

      I discovered that the LifecycleConnector JSON isn't correct when we have a special char in some content title (like a breakline char).
      Here is a patch to fix this by using the json-simple library to generate the json tree.

        Gliffy Diagrams

        1. 2011-09-06-ECMS-2688.patch
          7 kB
          Pham Duy Dong
        2. json-simple-migration.patch
          3 kB
          Benjamin Paillereau

          Activity

          Hide
          dongpd Pham Duy Dong added a comment -
          Show
          dongpd Pham Duy Dong added a comment - 2011-09-06-ECMS-2688.patch proposed
          Hide
          minh.dang Minh Dang added a comment -

          Patch validate. Please commit it.

          Show
          minh.dang Minh Dang added a comment - Patch validate. Please commit it.
          Hide
          ci-server CI Server added a comment -

          Integrated in ecms-trunk-ci #1642
          ECMS-2688 (Revision 73440)

          Result = SUCCESS
          dongpd :
          Files :

          • /ecms/trunk/ext/authoring/services/src/main/java/org/exoplatform/wcm/extensions/component/rest/LifecycleConnector.java
          Show
          ci-server CI Server added a comment - Integrated in ecms-trunk-ci #1642 ECMS-2688 (Revision 73440) Result = SUCCESS dongpd : Files : /ecms/trunk/ext/authoring/services/src/main/java/org/exoplatform/wcm/extensions/component/rest/LifecycleConnector.java

            People

            • Assignee:
              dongpd Pham Duy Dong
              Reporter:
              bpaillereau Benjamin Paillereau (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response:

                Time Tracking

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

                  Development