This page contains a listing of features that follows the structure of the JSR-314 JSR document. This page is a sub-document of V3WebTier.

SubCategory: Page Author Experience - Ed

• dynamic reloading on change of managed class
• Easier web application layout. Inspired by RoR, Phobos
• HTML based development (ala Tapestry; Facelets helps)
• First class support for "Environment" concept, as in Rails: Development,Test,Production

SubCategory: Component Development - Ed

• enable building custom components without tag handler, faces-config.xml and tld - perhaps annotations use within component class.
• First class support in JSP for JSF components
• Stronger guarantee of component interoperability between UIComponents from different vendors
• use of annotations in custom components.
  • annotations for persisting member variables (@SaveState)
  • annotations to help renderers - @Attribute("target")
  • strong support for annotations for defining a component and building the necessary wiring e.g. so you can just do @Property(el=true, saveState=true), or @Validator...
• Support for associated resources that go along with a component. Make it easy to bundle:
  • scripts
  • images
  • stylesheets
• Component aggreggation

SubCategory: Managed Bean Development - Ryan

• Generalizing Managed Beans so they can be used in the general web tier -> PENDING EG
• Leverage annotations to declare a POJO a managed bean -> PENDING EG

SubCategory: Renderer Development - Roger

• Declarative format for defining renderers - perhaps .tag files?
• APIs for rendering script content. Targets the same requirements targeted by shale-remoting.

SubCategory: Application Development - Ed

• avoid the "everything is a POST" syndrome - explore caching
• bookmark support
• error handling
  • what's needed is a pluggable exception handler so that an application can define a centralised exception configuration that deals with persistence, business AND UI.
• Annotations as in shale-tiger extensions.

SubCategory: State Saving - Ryan

• saving page deltas -> PENDING EG
• mostly "stateless" state saving -> PENDING EG
• rogerkeays> Reuse component state available from templates -> PENDING EG

Subcategory: UI features - Roger

• Easy customizable theme/skin API. Skinability Framework, that includes Skin parameters API, dynamically generated CSS and Images using Skin parameters (related to Resource Framework), easy use of Skin parameters from pages and Components.
• Build in commonly used validators such as:
  • E-mail address
  • URL:
  • Credit card number

Subcategory: Request Processing Lifecycle - Roger

• update parts of the component tree (example: DynaFaces)
• standardize Ajax support in specification (probably with some javascript library)
• Page Actions: Ability to say, "when this page loads, invoke this action". (Generalize this to other kinds of actions)

Misc - Ryan

• JMX tooling
  • Unknown - need to read up on JMX. We've done some initial requirements and have captured them in the issue tracker. This isn't a business or spec requirement, but a nice-to-have.
• rewriting config system to use DOM
  • config system to use DOM -> DONE
  • optionally create a merged DOM based off all parsed DOMs - 2 weeks
• additional performance work
  • always in progress