Uploaded image for project: 'CRISP'
  1. CRISP
  2. CRISP-36

When a Spring's HttpEntity is passed through ExchangeHint from cms webapp, the HttpEntity cannot be recognized by CRISP core due to classloader issue

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 2.1.1
    • Fix Version/s: 2.1.2
    • Labels:
      None
    • Similar issues:

      Description

      Even if the crisp api jar is shared and so even if you can invoke crisp core in site war through the shared api jar, the spring HttpEntity object is instantiated from cms war and passed into the crisp core (in site). Example: when crisp is used with post method in external document picker plugin.

      As a result, two different classes for HttpEntity was communicating, which is improper.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                wko Woonsan Ko
                Reporter:
                wko Woonsan Ko
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: