PageFlowMinutes20070327

Page Flow Content - March 27 2007

Contents


Attendees:

Sandip, Deva, Joelle

Purpose:

To define the overall architecture in which FacesModel contents for a given FileObject can be viewable in the Page Flow Editor.

Architecture:

Four new interface/classes will be added. The first three interfaces/classes all exist with web/jsf/navigation.

  1. PageContentModelProvider - An interface with only one menthod getPageContentModel(FileObject obj)
  2. PageContentModel - An abstract class that contains the components (PageContentItems) to be specified in a give page. Also allows for registered listeners.
  3. PageContentItem - Each content item has the following attributes (name, icon, outcome|action, actions)
  4. PageContentModelSupport - implements PageContentModelProvider. It is to exist in visualweb/navigation and can therefore dependency on visualweb/insync. It will use a facesmodel to create instances of PageContentModel. This class will be registered into the lookup via Meta-inf services.

PageFlowController will check for any registered PageContentModelProvider. Foreach provider it will call getPageContentModel, passing the fileobject of the faces-config. If the provider returns null, it is assumed the that PageContentModelProvider does not "know" the given fileobject. It will iterate through the providers until a model is given. Once the model is given, the PageFlowController will use the model to populate a page in the scene.

This documentation can be used to setup a provider.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo