Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Refactor InvokerPortlet to use factory pattern rather than prototype pattern to simplify the interface

Description

Using prototype pattern force us to put some extra logic inside InvokerPortlet interface. From portlet container's point of view, this is a bad idea, since the portlet should not in charge of creating copies of itself. It is container's job.

By using factory pattern, we can push out the creation logic into factories, which are parts of container.

Activity

Show:

EdG April 19, 2013 at 5:20 PM

Hello everyone! We are in the process of removing component "Portlet" from LPS. Please replace this issue's component, "Portlet", with a new component. There are over 200+ components, in the newly organized component list. Also, make the necessary adjustments to affected filters. Thanks!

Michael Saechang February 29, 2012 at 2:25 PM

Committed on:
6.1.x GIT ID: 5d66e9d31a4f4a9d2e48aac9c646608bb9777471.
6.2.x GIT ID: 050ad54eac2f36ee0153135547d532844e63b631.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Branch Version/s

6.1.x

Backported to Branch

Committed

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created February 23, 2012 at 2:41 AM
Updated June 24, 2023 at 3:59 PM
Resolved April 24, 2012 at 2:08 PM