Categories for issues from

EZComp and PDL

280,273,274,296

* Complete metadata specification

* JSR-273 integration

* When rendering a resource, assume #{this} in EL Expressions.  Now that
  I think about this more, I'm not sure this is the right thing, but I
  want to capture it anyway.

* make it so there is BeanInfo for all components

* Make it possible to support new kinds of attached objects

* Standard API for Facelets

  - Decide which com.sun.facelets classes should be refactored into
    javax.faces.webapp.pdl.facelets classes

  - Update the schema document for facelet taglibs to include a similar
    fidelity to that found in a JSP TLD file.  This information is
    strictly advisory.

    Make a tlddoc tool that uses this syntax to generate something like
    tlddocs.

  - Move javax.faces.webapp.pdl.PDLUtils static methods onto ViewHandler

  - Move PageDeclarationLanguage from Application to ViewHandler

  - Do a thorough traversal of the JSP spec, and, for each
    concept/feature therein that has an analog in Facelets, make sure
    the spec prose for that concept/feature is written.

  - Make sure the JSTL tags implemented in Facelets work exactly as
    expected when compared to the real JSTL.

Client Side and Ajax

488,304,293,302,49

State

485,146,295,139,340,360

- Complete specification of state management enhancements

- Annotation for attributes that should be included in state

Validation and Conversion

475,480,494,470,481,482,52,1,426,448

Navigation

455,484,127,487,179,200,454,359,419

* make sure you can use JSF code on an "error page" declared in the
  servlet way
.
* Preserve FacesMessage across redirect (flash scope to the rescue).

Exception Handling

248,291,476

* Research mojarra thrown exceptions and make sure all possible relevant
  information is not lost.

Events

240,332,473

* Shale ViewController events?

* Verify that performance impact of event system is acceptable

Class Hierarchy

441,322,245,453,143

* Interface for DataFlyweight

* Generify Validator and Converter

* Fix UIData.doTreeTraversal

- Test tree traversal very rigorously.

Config System

334,121,319,261,287

* Make 313 come into synch with Servlet 3.0

* metadata-complete just applies to top level faces-config.xml, and one
  in META-INF/classes, not to ones in jar files, and for annotations only.

* Consider automatically finding navigation.xml and managed-beans.xml
  automatically.

* Expose read only DOM of application configuration resources

Development Experience

97,313,314

* Collect complete list of cases to catch with issue 314.  Consider
  using treeWalker to make assertion about the tree after each phase of
  the lifecycle.

* Make sure our 313 story is compatible with what Servlet 3.0 ends up
  with.

* Be as concrete as possible regarding script based artifacts.

Attributes and Properties

478,170,451,238,353,430,424,237,228,450

Value Handling

428,425

EL

493,457,262,320,422,323

Context

358

ViewHandler

260

- Specify ViewHandler selection strategy vis a vis facelets or JSP

Rendering

42,316,468

From 20080806

* Nested content inside of <h:output{Style,Script}> is retargeted

UIData

236

=> edburns make sure to include Manfed Riem's requirements document.
   Make sure to invite David Lloyd and Mike Youngstrom to the conf call.

=> Make sure to include Hans Bergsten discussion from JSR 127

I18N,L10N,A11Y

345,201

* h:message(s) and screen readers

* screen readers in general

Managed Beans

336,140

- At what point in the faces-config for a managed bean, is it valuable
  to have EL.  Assert that if you specify an "eager" managed bean,
  putting an EL expression inside <scope> is invalid.

- Eager: what happens when the eager attribute is present on a bean that
  is not application scoped.

- Specify that scope==session and eager *does* work.  Can be implemented
  using our existing sessionCreated listener.

Naming

333,212,161

Security

26

- CSRF protection using random token

- Bring forward "javascript:" urls fix from 1.2

Javadocs

417,242,266

- Exhaustive list of new features that *are* exposed in JSP, make sure
  to state that if a feature is not explicitly called out as being
  exposed in JSP, it is *not* exposed in JSP.
   

-- Main.edburns - 21 Oct 2008