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

Move the dynamic filter logic from the display context to the AssetPublisherUtil class

    Details

      Description

      With moving the logic to the display context, the API became pretty request object dependent which is not that good as we cannot really use that from a service, for example exporting importing the Asset Publisher portlet on which we're working as a side project.

      On the other hand, in this way the place of the logic for the dynamic and the manual filtering are at different places. (The manual one is in the AssetPublisherUtil class where we put the logic of the dynamic one originally.) We think, that should be consequent and have the two login reachable through the same class.

      So at the end, we would need an API through which both of the manual and dynamic filtering can be reached without a request object if the process cannot have a request object in place.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              anthony.chu Anthony Chu
              Reporter:
              zsolt.olah Zsolt Oláh (Inactive)
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.0.0 Beta 2