Hi Manfred, any chance the code gen will be extended
in the near future towards tag class and renderer generation as well?
I am highly interested into it.
Tried to move towards it a week ago, but gave up due to maven issues
(and time constraints to look deeper)
I am currently helping myself out with code snippets
to generate most of the boilerplate code.
Which in my usecase works better,
but as you mentioned moving most of the boilerplate
generation towards a decend codegen would help tremendously
especially due to the api breakage of jsf 1.2
in certain areas.
Werner
Manfred Geiler schrieb:
Dennis, Lance,
I am indeed of the opinion that is is NOT OK to modify this generated
code parts.
Code generation will get importance again when we do the 1.2 port.
And: Code generation is still important and convenient for coding new
tomahawk components. Well, nobody seems to use it by now. Reason might
be (no, I'm sure it IS) the lack of docs. Yes, Lance, you are right,
there are no docs. Mea culpa.
And in defense I can not even say it's self-explaining. Because it is
not! ;-)
Ok, I give you a very short intro:
Codegenerator can be used by doing a "mvn clean install
-Pregenerate-component-code"
You can try it in core/api for instance.
Base for the generation of these code parts is an according xml file
that looks like this:
http://svn.apache.org/viewvc/myfaces/core/trunk/api/src/main/java/javax/faces/component/html/HtmlCommandButton.xml?view=markup
and sits in the same src dir as the component's java file.
(which is nonsense and should be in a config folder according to the
maven standard dir layout, of course)
There are some quirks: No dtd or xsd, and so on
But: it works! And it did a great job in the early days of MyFaces.
HTH and thanks for your interest in this nostalgic thingy :-)
Manfred
