[jsr-314-open] Providing the ability to instantiate EzCompcomponents in Java code

[Norbert Truchsess]

Am Sonntag, den 02.08.2009, 17:57 -0400 schrieb Kito Mann:
> FYI, the component class is determined by the component type already
> -- no need to expicitly specify it. In other words, if you specify a
> component type for <component:implementation>, the Java class with the
> matching type will be used.
> 

you are right, just checked this, it just works ;-)

What didn't work for me was binding this component to a managed bean by
using the binding-attribute. We havn't specified whether this should
work or not (the spec doesn't mention component-binding for
composite-components at all). Just opened a spec-issue for this:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=600

- Norbert

> Sent from my iPhone
> 
> 
> http://www.jsfcentral.com
> http://www.Virtua.com
> 
> 
> 
> On Aug 2, 2009, at 5:49 PM, "Lincoln Baxter, III"
> <lincolnbaxter at gmail.com> wrote:
> 
> 
> 
> > On Sun, 2009-08-02 at 12:04 +0200, Norbert Truchsess wrote:
> > > What do you mean by 'multiple class implementations'?
> > > 
> > 
> > More than one Java Class file per XHTML markup component -- but as
> > Kito suggested, I don't see much use in that, so your description of
> > specifying the Java class in the <component:interface> sounds good.