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

Add different strategies for non-serializable wrapping on weblogic

    Details

      Description

      Currently, we wrap all request attributes to prevent NotSerializableException (see: LPS-26657) due to weblogic feature to serialize request attributes on getAttribute(). Since this feature might be turned off, this improvement introduce new property with following values:

      + NONE - no wrapping is done at all; when weblogic is (somehow) set to work without doing this serialization; this gives best performances as nothing is wrapped.

      + UNSERIALIZABLE_ONLY - wrapping is done only for objects that can't be serialized on setAttribute() - note that weblogic actually performs this on getAttribute() (which generally happens more often, but its more correct); this gives worst performances as we trigger additional serialization.

      + ALL - wrapping is done for all objects - when this weblogic feature can not be set, so we simply want to protect ourselfs from failing.

      For safety reasons, we can default to ALL, and user can always have they way to get better performance.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                david.truong David Truong
                Reporter:
                igor.spasic Igor Spasic (Inactive)
                Recent user:
                Shalaka Tendulkar
                Participants of an Issue:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  6.2.0 CE M5