Versions Compared

Old Version 11

changes.mady.by.user Michael Ivanov

Saved on

compared with

New Version Current

changes.mady.by.user Jim Helwig

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

...

Note
titleHow Many Times Can an Application be Published?

Can a portlet application be published more than once? Does the current object model support this?
~pkharchenko Peter Kharchenko (Deactivated): I don't see why not. Unique deployment and definition Ids exist for both applications and portlets. I've only glanced at the DB schema, but it doesn't look like there are problems at that level either.

...

  • Show portlet categories (filtered according to user permissions)
  • Allow user to select portlet by browsing categories/sorting or searching
  • Allow user to modify Portlet Preferences (once again, according to permissions)
  • Hand over configured Portlet Entity for layout placement
Note
title[~mvi@immagic.com]: Portlet entity/window relationship

We currently have both portlet entities and windows user-scoped. I have been thinking that windows should not depend on user IDs directly because they have a dependency on them through entity IDs

...

Although the view will differ because of permissions, the same module can be used to present UI for modifying/setting portlet preferences during publish and subscribe steps.

Groups Manager Servant refactoring

Refer to Portlet Features#PortletMode_Servant
One of the common reusable components is the Groups Manager Servant that currently extends the uP2 multithreaded channel adapter.
In uP3 the servant needs to be rewritten to support JSR-168. The goal is to preserve the code with the existing business logic as much as possible. Some of the components like permissions from org.jasig.portal.channels.groupsmanager.permissions package could easily be reused without modifications,some of them need to be replaced, for example, ChannelRuntimeData with PortletRequest, ChannelStaticData with PortletContext, etc. The entire logic of CGroupsManager channel has to be rewritten in a portlet application.
The following interfaces and classes from different packages are currently used by the uP2 servant:

  • A couple of services such as AuthorizationService, EntityNameFinderService, GroupService, EntityPropertyRegistry from org.jasig.portal.services
  • A few types from org.jasig.portal package like IServant, IPermissible, EntityTypes, EntityIdentifier
  • Lots of components from org.jasig.portal.security such as IPerson, IAuthorizationPrincipal, IAuthorizationService, IPermission, IPermissionPolicy, IUpdatingPermissionManager