Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-40379

Run SPIAgentSerializable deserialization under corresponding plugin classloader for plugin portlets

    Details

      Description

      For core portlets and liferay SDK plugins, this is not necessary, because we use Serializer/Deserializer to serialization/deserialization, which keeps the classloader info in annotation. The deserialization process knows exactly which classloader to use.

      But for third part libs, like JSF, Spring MVC, etc, a lot of them depends on thread context classloader to do the deserialization, to satisfy them we have to tangle the context classloader around the deserialization logic.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                brian.chan Brian Chan
                Reporter:
                shuyang.zhou Shuyang Zhou
                Participants of an Issue:
                Recent user:
                Esther Sanz
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  6 years, 8 weeks, 6 days ago

                  Packages

                  Version Package
                  6.2.0 CE RC2