facelets@myfaces [was: facelets taglib for tomahawk and sandbox]

[Mario Ivankovits <ma...@ops.co.at>]

Hi!
> If you, or anyone else for that matters, want to fix /add more
> handlers to the projects feel free to tell me and I can add you as
> members right away!
>   
What about a MyFaces Facelets (MyFaces MyFacelets ;-) ) project at all,
not only for the taglibs we might host there then (as long as the
generator is not live) but also for some Facelets dependent stuff.

For example I'd start with my dynamicInclude component which allows to:
1) add xhtml fragments at render-time instead of compile-time - this is
required if you'd like to include e.g. app-configured fragments to the
JSF tree which might change from one request to the next.
2) add xhtml fragments to "old" JSP/JSF pages - this allows you to
slowly migrate your app to facelets.

This component is searching a home :-)

Ciao,
Mario

Re: facelets@myfaces [was: facelets taglib for tomahawk and sandbox]

[Andrew Robinson <an...@gmail.com>]

I would be a proponent for a new tomahawk-like project to house
facelets-only projects (tag handlers and components). I could even
move my annotation deployment code from jsf-comp over to myfaces for
such a project.

I'd be willing to help setup the projects to use the trinidad maven
plugin for this (for the component generation), if desired, since I
have done it before. I don't know anything about the builds though and
how they get run (including snapshots getting into the repository and
release management).

-Andrew

On 10/24/07, Mike Kienenberger <mk...@gmail.com> wrote:
> Once I get back to JSF work, I'd happily contribute to a MyFaces
> Facelets project.   As I've said in years past, I don't know how to
> set up a maven project, but once someone set up the infrastructure for
> such a project, I'd be able to help with the rest.
>
> The same goes for the MyFaces commons project.   If someone could set
> up the infrastructure, then I could start working on the rest.
>
> On 10/24/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > Hi!
> > > If you, or anyone else for that matters, want to fix /add more
> > > handlers to the projects feel free to tell me and I can add you as
> > > members right away!
> > >
> > What about a MyFaces Facelets (MyFaces MyFacelets ;-) ) project at all,
> > not only for the taglibs we might host there then (as long as the
> > generator is not live) but also for some Facelets dependent stuff.
> >
> > For example I'd start with my dynamicInclude component which allows to:
> > 1) add xhtml fragments at render-time instead of compile-time - this is
> > required if you'd like to include e.g. app-configured fragments to the
> > JSF tree which might change from one request to the next.
> > 2) add xhtml fragments to "old" JSP/JSF pages - this allows you to
> > slowly migrate your app to facelets.
> >
> > This component is searching a home :-)
> >
> > Ciao,
> > Mario
> >
> >
>

Re: facelets@myfaces [was: facelets taglib for tomahawk and sandbox]

[Mike Kienenberger <mk...@gmail.com>]

Once I get back to JSF work, I'd happily contribute to a MyFaces
Facelets project.   As I've said in years past, I don't know how to
set up a maven project, but once someone set up the infrastructure for
such a project, I'd be able to help with the rest.

The same goes for the MyFaces commons project.   If someone could set
up the infrastructure, then I could start working on the rest.

On 10/24/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> > If you, or anyone else for that matters, want to fix /add more
> > handlers to the projects feel free to tell me and I can add you as
> > members right away!
> >
> What about a MyFaces Facelets (MyFaces MyFacelets ;-) ) project at all,
> not only for the taglibs we might host there then (as long as the
> generator is not live) but also for some Facelets dependent stuff.
>
> For example I'd start with my dynamicInclude component which allows to:
> 1) add xhtml fragments at render-time instead of compile-time - this is
> required if you'd like to include e.g. app-configured fragments to the
> JSF tree which might change from one request to the next.
> 2) add xhtml fragments to "old" JSP/JSF pages - this allows you to
> slowly migrate your app to facelets.
>
> This component is searching a home :-)
>
> Ciao,
> Mario
>
>