Specify how iterating components assign HTML ids to their constituents. This will enable JavaScript addresability

leewas> 1. Allow specify scope of managed-bean to portlet-scope
leewas> session or application-scope session in portlet environment.

leewas> 2. Support portlet IPC.

Consider standardizing Creator's DataProvider^?.

arobinson74> ..:componentId

arobinson74> The ".." would tell findComponent that it should find arobinson74> the naming container of the current component and go up arobinson74> one naming container above that. So a client ID of arobinson74> "A:B:C:D" the component could find "B" by using "..:.." arobinson74> instead of having to give a full path of ":A:B".

vajav> * Force implementations to make ALL attributes of the html vajav> elements stuff is rendered to accessible! E.g. the size vajav> attribute of selectManyMenu (who the f*** thought it would be vajav> good to render a menu supposed for selecting more than 1 entry vajav> at time with a fixed size of 1 ???) .

vajav> * Make the html output xhtml 1.1 strict compatible - currently vajav> there are problems with the ids & client side state saving.

vajav>* Don't use javascript if it isn't absolute necessary (e.g. for vajav> posting forms)!

quilleashm> I would like to see a FacesEvent^?.get/setParent() that quilleashm> must be used when wrapping an event, usually in quilleashm> queueEvent(). For example UIData in the RI wraps up quilleashm> events from children in it's own event class so it can quilleashm> set it's own index when the event gets quilleashm> broadcast. Ancestors of the UIData cannot then "see" the quilleashm> original event. Implementation would just add a quilleashm> getParent() to FacesEvent^? and then setting either with a quilleashm> setter or a constructor overload. Components can then quilleashm> walk the entire event stack to look for the real event of quilleashm> interest.

String foo = (String) ((SomeBean^?) FacesContext^?.getCurrentInstance() .getExternalContext().getApplicationMap().get("bean")).getConfig() .get("my.config.variable");

or

String foo = ${bean.config['my.config.variable']}

* Ability to specify <h:form> method attribute (GET or POST) * Configurable default timezone for <f:convertDateTime/> * Configurable default styles for <h:messages/> * Make UISelectMany^? choose a converter-for-class for E from a List<E> genericized type * Ability to define converters for annotated classes (e.g. @Entity)

Fix dataTable!

In addition to this special TCK to validate/certificate Component Libraries for compatibility.

Validation Messages must have Client-side API to allow seamless Client and Ajax style validations.

- Examine Oracle JDeveloper's JSF support for mobile devices. It appears that for each page being developed you can create a view for desktop computers and a view for mobile devices. They might even provide browser detection for displaying the correct view. Being able to develop a single JSF 2.0 web app that can target both desktop and mobile devices would be invaluable. -- Main.rdelaplante - 01 Apr 2007

- Integrate AOP features to the IOC container; for example ability to intercept methods that fit the *Save pattern.

WebBeans (JSR-299)

Design-Time API for JavaBeans (JSR-273)

Design-Time Metadata for JavaServer Faces Components

The following technologies will most likely need revision to coordinate with this specification:

• Portlets

• WebBeans (JSR-299)

• The Validation Specification (JSR-303)

• Design-Time API for JavaBeans^? (JSR-273)

• Design-Time Metadata for JavaServer Faces Components (JSR-276)

• Java API for RESTful Web Services (JSR-311)

Category: Servlet SPEC Requirements

  Make it so you don't have to map the FacesServlet in the web.xml all
  the time.

  Specify how ordering of ServletContext listeners works in web.xml and
  in TLD files in jars in WEB-INF/lib

  Servlet support for File Upload.

  Programmatic Access to web.xml (like what Jetty does). Obviate the
  need for writing a web.xml parser.

  Login/logout

  Container Managed Authentication overhaul (also mentioned in JSR-252-EG list)

  Error reporting line precise (down to servlet)

Category: JSP SPEC Requirements

  JSP.eval()

  Make JSP recognize JSF components in a first class manner.

Category: EL SPEC Requirements

  Investigate plugging in other ELs into JSP (OGNL)?

  Expanded read/write support in JSF el

  Better type conversion, like OGNL

Category: Process

  Align spec versions with Java EE 6

  Make it possible for someone to pass the JSF 1.2 TCK with out
  implementing deprecated methods.

  Separate Standard HTML Renderkit from the JSF 2.0 effort into a
  separate spec and/or JSR. Keep UICommand, UIData, etc in core spec.


Category: Ease Of Development

note: make sure to talk to users of Internet Service Providers.  For people whose development environment is 
hosted by an ISP, we have to make sure those users are happy.

	SubCategory: Page Author Experience

		- better support for .tag files
		- HTML based development (ala Tapestry; Facelets helps)
		- better way to "componentize" page parts 
		  (better than jsp:include)

		- Easier web application layout. Inspired by RoR, Phobos

		- Zero deployment time for all artifacts, including faces-config.xml
		  (also mentioned on JSR-252-EG)

		- implementations check for changes in faces-config.xml for 
		  additional elements (such as nav handlers, components, etc..)..
		- Grizzly support will deinitely help here.
		- ability to inspect RenderKit for its Renderers at run time.

		- Less configuration, more convention

		- First class support for "Environment" concept, as in Rails:
		  Development,Test,Production

	SubCategory: Component Development

		- enable building custom components without tag handler,
		  faces-config.xml and tld - perhaps annotations use within
		  component class.

		- use of annotations in custom components.
		  Examples:
			 - annotations for persisting member variables (@SaveState)
			 - annotations to help renderers - @Attribute("target") 

	SubCategory: Managed Bean Development
		
		- annotations for dependency lookups
		  Example: @Lookup("#{param.id}")

		- Generalizing Managed Beans so they can be used in the general web tier

		- Leverage annotationsto declare a POJO a managed bean

		- Dialog/Conversation/Flash/Scope: there is currently no way to
		  insert a scope between request and session. (WebBeans overlap)

	SubCategory: Renderer Development 

		- Declarative format for defining renderers - perhaps .tag files? 

		  Ability to write a renderer without resorting to out.println():
		  declarative rendering. See what Ajax4JSF does, as well as Ken
		  Paulsen's JSFTemplating. (Also mentioned in JSR-252-EG where it
		  is suggested that the writer is moved into a full SAX-compatible
		  handler, and where Adam suggests templating.)

		- APIs for rendering script content. Targets the same requirements
		  targeted by shale-remoting.

	SubCategory: Tag Handler Development

		- We already help by generating tag handler classes and tld
		  Take this a step further and remove the need to generate
		  these completely.  JSP spec change - programatic registration
		  of tag classes would allow JSF runtime to register tags as
		  it parsed faces-config.xml.

	SubCategory: Application Development

		- passing values from page to page
		- additional scopes (process, dialog, conversation, etc..)
		- avoid the "everything is a POST" syndrome - explore caching
		- error reporting line precise (down to servlet)

	Better Error reporting, like what you get with Tapestry (also in
	JSR-252-EG, where it was said: any time there is an error in *any*
	part of the lifecycle, the user should see not just a cryptic stack
	trace, but also the component - including file and line number - that
	triggered the problem, the EL expression that was being evaluated -
	including the part of the EL expression that triggered the problem,
	etc. Diagnosability for state saving is also important. On this point,
	Gavin King wants to have centralized error handling, with an
	interception point, perhaps using navigation rules, to help handle
	errors.)

		- control inclusion (or not) of jsessionid in URL via some external 
		  attribute
		- bookmark support
		- annotations for validation
		- better faces-config support for lage apps

Category: Performance

	SubCategory: State Saving

		- saving page deltas
		- mostly "stateless" state saving

		- Re-do UIComponent State Saving, with a view towards making stateless
		  components the default.

Category: Adoption

  Subcategory: UI features

		- Easy customizable theme API

Category: Features

  Subcategory: Request Processing Lifecycle

	 Ajax support: Specification for client side event mechanism.

		- update parts of the component tree (example: DynaFaces)
		- standardize Ajax support in specification (probably with 
		  some javascript library)

		- Using javascript document.write() to build the component layout
		  on the client side is also show stopper, because document is
		  closed already during the Ajax requests/responses.

		- Components with rendered="false" have no placeholders in the
		  browser DOM. As a result, component becomes rendered during the
		  Ajax request, but there no place in the DOM to put it after Ajax
		  response.


	 Handle Duplicate Button Presses
	 gracefully. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=31

	 Lost update
	 problem. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=70

	 Bookmarkable JSF pages

	 Multi-thread web applications: popups, frames, iFrames, etc.

	 Shale: viewController

	 Page Actions: Ability to say, "when this page loads, invoke this
	 action".

	 Alternative, Statless lifecycle

	 Transaction annotations.
	 
	 Make Lifecycle Extensible/Customizable beyond PhaseListeners (Martin Marinschek)
	 
	 Look at generic 'Visitor Pattern' for Lifecycle Processing (Martin Marinschek)

  Subcategory: UI Components

	 Support for associated resources that go along with a component. Make
	 it easy to bundle:

		*
		 o scripts
		 o images
		 o stylesheets

	 Calendar component

	 Tree component (Gavin King also wants this)

	 Tabbed view 

	 File upload component

	 Ability to visit ever node, even every cell in a datatable.

	 Ability to have a "component" EL implicit object
	 
	 Scaffolding UIComponents/Models for Rapid Development with EJB3 (BeanEditor/Seam UI/Rails)

  Subcategory: Navigation

	 Allow EL evaluation within navigation cases to enable bookmarkable
	 links after action invocation.
	 
	 Include EL evaluation with Navigation Rules and for Update Phase (Gavin King)
	 
	 Bind navigation cases to exception or response codes (web.xml)

  Subcategory: Validation/Conversion

	 Decent inter-component and form-level validation

	 Integrate with Validation JSR

	 Need a more powerful way to decorate input fields when validation or
	 conversion errors occur, perhaps using facets on h:form

  Subcategory: View Description Language

	 Include Facelets/JSFTemplating/Tapestry 5 API in Spec.
	 
	 Retain ability to use alternate ViewHandlers
	 
	 Separate View mapping-related methods from ViewHandler
	 (ActionMapper or ViewMapper based on FacesContext)

  Subcategory: EL

	 Allow resource bundles to contain EL expressions

	 Allow faces messages to contain EL expressions 

  Subcategory: Security

	 JAAS support

	 Ajax security

	 Integrate with servlet login/logout.