Re: Generating a facelets myfaces.taglib.xml file

2005-08-01 Thread Sean Schofield
Do we need to keep the old xml files in SVN? Ex. HtmlCommandSortHeader.xml. I'm about to add a new property to the component. Do I have to maintain the XML file? That seems like a pain. I understand the usefulness of generating the code the first time using the XML but I don't understand the

Re: Generating a facelets myfaces.taglib.xml file

2005-08-01 Thread Mike Kienenberger
It would be good to provide a single authoritative source of information. If you want to easily support other view handlers, you may need to generate some configuration files for them. For example, facelets needs configuration information in this format: tag

Re: Generating a facelets myfaces.taglib.xml file

2005-08-01 Thread Sean Schofield
I also think that most of the component documentation could have easily been generated from the xml file using your template instead of having individuals go through and manually type in all of that information. Perhaps. Lately I've been thinking about a way to automate this by using the

Re: Generating a facelets myfaces.taglib.xml file

2005-07-29 Thread Bruno Aranda
In my personal experience I have used the codegen stuff of myfaces to create new components, because you only define the xml and the component is created magically :-). I know there is also the stuff to generate the taglib for the wml stuff, but this one, IMO, could be eliminated and only we

Re: Generating a facelets myfaces.taglib.xml file

2005-07-29 Thread Bill Dudney
Could someone provide a quick overview of the code generation stuff. I'd hate for us to drop it completely if its still useful. If its not useful then lets get rid of the xml files and the comments that say 'don't edit this code'. My $0.02 worth. TTFN, -bd- On Jul 28, 2005, at 8:32 PM,

Re: Generating a facelets myfaces.taglib.xml file

2005-07-29 Thread Manfred Geiler
It's rather simple and still useful IMO. You just define the path of your (new) component in the according build.properties (now called codegen.properties) and run one of the targets generate-single-api-component, generate-single-impl-component or generate-single-components-component depending on

Re: Generating a facelets myfaces.taglib.xml file

2005-07-28 Thread Sean Schofield
No code generation is going on in the new build AFAIK. I've mentioned this a few times but everyone says that we are fine - let's release, etc. :-) There are the xml files which result in the generated code do not alter portions of the source. Do we really need to keep these around? They seem

Generating a facelets myfaces.taglib.xml file

2005-07-27 Thread Mike Kienenberger
What ever became of the codegen stuff? I was hoping to submit a patch to automatically build a myfaces.taglib.xml file for use with the facelets project, but I can't seem to find it anymore. facelet-taglib namespacehttp://myfaces.apache.org/extensions/namespace

Re: Generating a facelets myfaces.taglib.xml file

2005-07-27 Thread Martin Marinschek
must have been left out in the SVN reorg then - Sean, any comment on that? thanks, MartinOn 7/27/05, Mike Kienenberger [EMAIL PROTECTED] wrote: What ever became of the codegen stuff?I was hoping to submit a patch to automatically build amyfaces.taglib.xml file for use with the facelets project,