Versions Compared

Old Version 8

changes.mady.by.user Eric Dalquist

Saved on

compared with

New Version 9

changes.mady.by.user Eric Dalquist

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • uPortal DAOs should provide a list of portlet applications that can be published.
  • The user selects a currently deployed portlet application and is provided with mapping options from data provided in the portlet.xml to uPortal 3's support for the features. These mappings will apply to all portlets in the published application.
    • Custom Portlet Modes
    • Custom Window States
    • User Attributes
  • What options should be given to a user for deleting a published portlet application
    • If a user deletes a mapping a list of published portlets based on the mapping should be displayed and the user should have the confirm that deleting the mapping will also delete those published portlets.

New Application Workflow Outline

This describes the interaction a portlet UI or XML based publishing tool would have with a set of high level portlet application publishing APIs.

  1. Get list of portlet application names (Web-App context names)
  2. Get declared PortletModes, WindowStates and User Attributes for a specified portlet application
    • Return this information as a single object
  3. Set the mappings for the PortletModes, WindowStates and User Attributes, a unique name must be specified.
    • Specify this information as a single object
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: 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.

...