[jsr-314-open] Providing the ability to instantiateEzComp components in Java code

[lincolnbaxter at gmail.com]

+1 .....again... ;) I really think this would be a feature nobody else provides, and a LOT of java component tree building happens at big companies.

Allows total control over the component tree 
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Roger Kitain <Roger.Kitain at Sun.COM>

Date: Fri, 31 Jul 2009 11:26:37 
To: <jsr-314-open at jcp.org>
Subject: Re: [jsr-314-open] Providing the ability to instantiate
	EzComp	components in Java code


+1
Since one can already create standard JSF components using Java.

Dan Allen wrote:
> This is a somewhat old request from Lincoln Baxter that I don't think 
> ever made it to the list. After reviewing the message, I too feel it 
> is worth discussing for JSF 2.1.
>
> ---------- Forwarded message ----------
> From: *Lincoln Baxter, III* <lincolnbaxter at gmail.com 
> <mailto:lincolnbaxter at gmail.com>>
> Date: Thu, Mar 5, 2009 at 10:25 PM
> Subject: Providing the ability to instantiate EzComp components in 
> Java code
> To: jsr-314-comments at jcp.org <mailto:jsr-314-comments at jcp.org>
>
> I feel there is value in the ability to instantiate an EzComp object 
> in Java so that a component tree can be built in a backing bean (or 
> other Class). JSF must be doing this in the background through 
> Facelets, so providing this ability in Java should not be too difficult.
>
> Referencing an object by its namespace should be sufficient:
>
> UIComponent comp = Application.createComponent(FacesContext, 
> "http://java.sun.com/jsf/composite/mynamespace:component" ) .
>
> Attributes would be assigned via the normal method:
>
> comp.getAttributes().put("rendered", false);
>
> This would greatly extend the reach of EzComp objects.
>
> Thanks,
> Lincoln
>
>
> PS... re-posted here on suggestion of Ryan Lubke