You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Mike Kienenberger <mk...@gmail.com> on 2005/07/27 23:19:32 UTC
Generating a facelets "myfaces.taglib.xml" file
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>
<namespace>http://myfaces.apache.org/extensions</namespace>
#foreach ($c in $componentList)
<tag>
<tag-name>$c.baseJSPTagName</tag-name>
<component>
<component-type>${c.componentType}</component-type>
#if ($c.rendererType)
<renderer-type>${c.rendererType}</renderer-type>
#end## if ($c.rendererType)
</component>
</tag>
#end## foreach ($c in $componentList)
</facelet-taglib>
========================
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Bruno Aranda <br...@gmail.com>.
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 should kept the generated taglib and maintain
it manually...
Bruno
2005/7/29, Sean Schofield <se...@gmail.com>:
> 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 like a maintenance nightmare. (I understand there
> use in the beginning but I'm confused about now.) Are we really ever
> going to generate that code again? I suspect things are already out
> of sync by now.
>
> Not sure what else requires codegen. I thought there was some WAP
> stuff too but I'm a bit confused on that area of MyFaces.
>
> sean
>
>
> On 7/28/05, Martin Marinschek <ma...@gmail.com> wrote:
> > must have been left out in the SVN reorg then - Sean, any comment on that?
> >
> > thanks,
> >
> > Martin
> >
> >
> > On 7/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > > 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>
> > >
> > <namespace>http://myfaces.apache.org/extensions</namespace>
> > > #foreach ($c in $componentList)
> > > <tag>
> > > <tag-name>$c.baseJSPTagName</tag-name>
> > > <component>
> > >
> > <component-type>${c.componentType}</component-type>
> > > #if ($c.rendererType)
> > >
> > <renderer-type>${c.rendererType}</renderer-type>
> > > #end## if ($c.rendererType)
> > > </component>
> > > </tag>
> > > #end## foreach ($c in $componentList)
> > > </facelet-taglib>
> > >
> > > ========================
> > >
> >
> >
>
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Sean Schofield <se...@gmail.com>.
> 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 source and TLD. Maybe that would be the next best thing at
this stage in the game.
> -Mike
sean
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Mike Kienenberger <mk...@gmail.com>.
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>
<tag-name>aliasBean</tag-name>
<component>
<component-type>org.apache.myfaces.AliasBean</component-type>
<renderer-type>org.apache.myfaces.AliasBean</renderer-type>
</component>
</tag>
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.
-Mike
On 8/1/05, Sean Schofield <se...@gmail.com> wrote:
> 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 point in keeping it
> around once that's done.
>
> sean
>
> On 7/29/05, Manfred Geiler <ma...@gmail.com> wrote:
> > 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 what kind of
> > component class files (API, Impl or Tomahawk) should be generated
> > ("injected").
> > The generation seems to be broken after the reorg. I will have a look
> > on that soon. Next week I'm on vacation, so it will be second week of
> > August.
> >
> > -Manfred
> >
> >
> > 2005/7/29, Bill Dudney <bd...@mac.com>:
> > > 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, Sean Schofield wrote:
> > >
> > > > 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 like a maintenance nightmare. (I understand there
> > > > use in the beginning but I'm confused about now.) Are we really ever
> > > > going to generate that code again? I suspect things are already out
> > > > of sync by now.
> > > >
> > > > Not sure what else requires codegen. I thought there was some WAP
> > > > stuff too but I'm a bit confused on that area of MyFaces.
> > > >
> > > > sean
> > > >
> > > >
> > > > On 7/28/05, Martin Marinschek <ma...@gmail.com> wrote:
> > > >
> > > >> must have been left out in the SVN reorg then - Sean, any comment
> > > >> on that?
> > > >>
> > > >> thanks,
> > > >>
> > > >> Martin
> > > >>
> > > >>
> > > >> On 7/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > > >>
> > > >>> 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>
> > > >>>
> > > >>>
> > > >> <namespace>http://myfaces.apache.org/extensions</namespace>
> > > >>
> > > >>> #foreach ($c in $componentList)
> > > >>> <tag>
> > > >>> <tag-name>$c.baseJSPTagName</tag-name>
> > > >>> <component>
> > > >>>
> > > >>>
> > > >> <component-type>${c.componentType}</component-type>
> > > >>
> > > >>> #if ($c.rendererType)
> > > >>>
> > > >>>
> > > >> <renderer-type>${c.rendererType}</renderer-type>
> > > >>
> > > >>> #end## if ($c.rendererType)
> > > >>> </component>
> > > >>> </tag>
> > > >>> #end## foreach ($c in $componentList)
> > > >>> </facelet-taglib>
> > > >>>
> > > >>> ========================
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > >
> > >
> >
>
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Sean Schofield <se...@gmail.com>.
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 point in keeping it
around once that's done.
sean
On 7/29/05, Manfred Geiler <ma...@gmail.com> wrote:
> 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 what kind of
> component class files (API, Impl or Tomahawk) should be generated
> ("injected").
> The generation seems to be broken after the reorg. I will have a look
> on that soon. Next week I'm on vacation, so it will be second week of
> August.
>
> -Manfred
>
>
> 2005/7/29, Bill Dudney <bd...@mac.com>:
> > 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, Sean Schofield wrote:
> >
> > > 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 like a maintenance nightmare. (I understand there
> > > use in the beginning but I'm confused about now.) Are we really ever
> > > going to generate that code again? I suspect things are already out
> > > of sync by now.
> > >
> > > Not sure what else requires codegen. I thought there was some WAP
> > > stuff too but I'm a bit confused on that area of MyFaces.
> > >
> > > sean
> > >
> > >
> > > On 7/28/05, Martin Marinschek <ma...@gmail.com> wrote:
> > >
> > >> must have been left out in the SVN reorg then - Sean, any comment
> > >> on that?
> > >>
> > >> thanks,
> > >>
> > >> Martin
> > >>
> > >>
> > >> On 7/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > >>
> > >>> 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>
> > >>>
> > >>>
> > >> <namespace>http://myfaces.apache.org/extensions</namespace>
> > >>
> > >>> #foreach ($c in $componentList)
> > >>> <tag>
> > >>> <tag-name>$c.baseJSPTagName</tag-name>
> > >>> <component>
> > >>>
> > >>>
> > >> <component-type>${c.componentType}</component-type>
> > >>
> > >>> #if ($c.rendererType)
> > >>>
> > >>>
> > >> <renderer-type>${c.rendererType}</renderer-type>
> > >>
> > >>> #end## if ($c.rendererType)
> > >>> </component>
> > >>> </tag>
> > >>> #end## foreach ($c in $componentList)
> > >>> </facelet-taglib>
> > >>>
> > >>> ========================
> > >>>
> > >>>
> > >>
> > >>
> > >
> >
> >
>
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Bill Dudney <bd...@mac.com>.
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, Sean Schofield wrote:
> 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 like a maintenance nightmare. (I understand there
> use in the beginning but I'm confused about now.) Are we really ever
> going to generate that code again? I suspect things are already out
> of sync by now.
>
> Not sure what else requires codegen. I thought there was some WAP
> stuff too but I'm a bit confused on that area of MyFaces.
>
> sean
>
>
> On 7/28/05, Martin Marinschek <ma...@gmail.com> wrote:
>
>> must have been left out in the SVN reorg then - Sean, any comment
>> on that?
>>
>> thanks,
>>
>> Martin
>>
>>
>> On 7/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
>>
>>> 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>
>>>
>>>
>> <namespace>http://myfaces.apache.org/extensions</namespace>
>>
>>> #foreach ($c in $componentList)
>>> <tag>
>>> <tag-name>$c.baseJSPTagName</tag-name>
>>> <component>
>>>
>>>
>> <component-type>${c.componentType}</component-type>
>>
>>> #if ($c.rendererType)
>>>
>>>
>> <renderer-type>${c.rendererType}</renderer-type>
>>
>>> #end## if ($c.rendererType)
>>> </component>
>>> </tag>
>>> #end## foreach ($c in $componentList)
>>> </facelet-taglib>
>>>
>>> ========================
>>>
>>>
>>
>>
>
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Sean Schofield <se...@gmail.com>.
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 like a maintenance nightmare. (I understand there
use in the beginning but I'm confused about now.) Are we really ever
going to generate that code again? I suspect things are already out
of sync by now.
Not sure what else requires codegen. I thought there was some WAP
stuff too but I'm a bit confused on that area of MyFaces.
sean
On 7/28/05, Martin Marinschek <ma...@gmail.com> wrote:
> must have been left out in the SVN reorg then - Sean, any comment on that?
>
> thanks,
>
> Martin
>
>
> On 7/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > 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>
> >
> <namespace>http://myfaces.apache.org/extensions</namespace>
> > #foreach ($c in $componentList)
> > <tag>
> > <tag-name>$c.baseJSPTagName</tag-name>
> > <component>
> >
> <component-type>${c.componentType}</component-type>
> > #if ($c.rendererType)
> >
> <renderer-type>${c.rendererType}</renderer-type>
> > #end## if ($c.rendererType)
> > </component>
> > </tag>
> > #end## foreach ($c in $componentList)
> > </facelet-taglib>
> >
> > ========================
> >
>
>
Re: Generating a facelets "myfaces.taglib.xml" file
Posted by Martin Marinschek <ma...@gmail.com>.
must have been left out in the SVN reorg then - Sean, any comment on that?
thanks,
Martin
On 7/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
>
> 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>
> <namespace>http://myfaces.apache.org/extensions</namespace>
> #foreach ($c in $componentList)
> <tag>
> <tag-name>$c.baseJSPTagName</tag-name>
> <component>
> <component-type>${c.componentType}</component-type>
> #if ($c.rendererType)
> <renderer-type>${c.rendererType}</renderer-type>
> #end## if ($c.rendererType)
> </component>
> </tag>
> #end## foreach ($c in $componentList)
> </facelet-taglib>
>
> ========================
>