Hi Leonardo,

I'm working on improving the documentation for the builder plugin.

AUIA, there were planned to be three modes for defining a component:
(a) hand-writing a component class
(b) auto-generating a subclass of a hand-written class
(c) auto-generating a class that used a hand-written class as a
"template".

For implementing myfaces-core, (c) is needed as we all agreed that we
cannot use a package-scoped parent, and the TCK forbids a public parent.

I see that the annotations on the classes in myfaces-core-1.1.x look
like this:
 * @JSFComponent
 *   name = "h:graphicImage"
 *   class = "javax.faces.component.html.HtmlGraphicImage"
 *   tagClass = "org.apache.myfaces.taglib.html.HtmlGraphicImageTag"
 *   desc = "h:graphicImage"

So clearly this set of attributes is triggering mode (c):
"template-based generation". 

How can (b) be triggered?

Regards,
Simon

Reply via email to