Uploaded image for project: '[Read Only] - CRISP'
  1. [Read Only] - 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

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • 2.1.1
    • 2.1.2
    • None

    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

          is backported by

          Bug - A problem which impairs or prevents the functions of the product. CRISP-37 [Backport 2.0.x] When a Spring's HttpEntity is passed through ExchangeHint from cms webapp, the HttpEntity cannot be recognized by CRISP core due to classloader issue

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. CRISP-38 [Backport 1.x] When a Spring's HttpEntity is passed through ExchangeHint from cms webapp, the HttpEntity cannot be recognized by CRISP core due to classloader issue

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Activity

            People

              wko Woonsan Ko (Inactive)
              wko Woonsan Ko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: