You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Mario Ivankovits <ma...@ops.co.at> on 2007/10/22 21:03:05 UTC
facelets taglib for tomahawk and sandbox
Hi!
I know, this has been discussed in lengthy already, but I'd like to warm
it up again.
I'd like to add the facelets taglib and tag-handler one can find all
around the net to our myfaces libs.
I found this a REAL pain to figure out all the required stuff to get
tomahawk and the sandbox running again with facelets - every newbe will
be lost, there are other problems one should solve and not to such
trivial stuff which requires a lot of searching.
I know, we have a wiki for this, but as far as I can see this is not
really maintained. And it is hard to maintain, we (I think I can write
WE here, sorry if not) developers prefer to work with svn and not with
any wiki page where you even can't be sure if the stuff compiles - and
it is much harder to remember the wiki page than lookup the resource in
your ide and fix some stuff.
I think the argument that only a component generator is safe enough to
create the taglib is not valid, if there are errors in the taglib or one
of its handler class they will uncover sooner or later, in the end, we
have a fully working drop-in-able tomahawk and sandbox stuff.
PLEASE, lets go that way!!
Ciao,
Mario
Re: facelets taglib for tomahawk and sandbox
Posted by Bruno Aranda <br...@gmail.com>.
On 22/10/2007, Mike Kienenberger <mk...@gmail.com> wrote:
> There are already "tomahawk-facelets.jar" files out there if you want
> to use something with drop-in support. See the wiki page for a link
> to Bruno's http://code.google.com/p/tomahawk-facelets project.
>
Yes, I decided to make available my little project with a tomahawk
taglib (after reinventing the wheel for the thousand time I guess)
getting the info from the wiki and around. I had to maintain the
library anyway for my projects, so why not make it open source and get
the help of the community for free :)
Cheers,
Bruno
Re: facelets taglib for tomahawk and sandbox
Posted by Bruno Aranda <br...@gmail.com>.
Done! Thanks Mario :)
Bruno
On 24/10/2007, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi Bruno
> > I have put your class in the sources.
> >
> Thanks!
>
> Unfortunately I don't know what I've done yesterday to not see a bug
> with my TagHandler.
>
> Please add this line "this.nextHandler.apply(ctx, aliasBean);" at the
> end of the apply method, so it should look like the following then:
>
> {
> aliasBean.setAlias(alias);
> }
>
> parent.getChildren().add(aliasBean);
> this.nextHandler.apply(ctx, aliasBean);
> }
> }
>
> Thanks!
> Ciao,
> Mario
>
>
Re: facelets taglib for tomahawk and sandbox
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi Bruno
> I have put your class in the sources.
>
Thanks!
Unfortunately I don't know what I've done yesterday to not see a bug
with my TagHandler.
Please add this line "this.nextHandler.apply(ctx, aliasBean);" at the
end of the apply method, so it should look like the following then:
{
aliasBean.setAlias(alias);
}
parent.getChildren().add(aliasBean);
this.nextHandler.apply(ctx, aliasBean);
}
}
Thanks!
Ciao,
Mario
Re: facelets@myfaces [was: facelets taglib for tomahawk and sandbox]
Posted by 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]
Posted by 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
>
>
facelets@myfaces [was: facelets taglib for tomahawk and sandbox]
Posted by 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 taglib for tomahawk and sandbox
Posted by Bruno Aranda <br...@gmail.com>.
Done! Thanks! I have put your class in the sources.
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!
Thanks,
Bruno
On 23/10/2007, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
>
> Please consider adding the following handler for the AliasBean to your
> project:
> (This is my first Tag-Handler, so I am not sure if there is a more
> elegant way - at least the AliasBean works here now)
>
> import com.sun.facelets.FaceletContext;
> import com.sun.facelets.FaceletException;
> import com.sun.facelets.tag.TagAttribute;
> import com.sun.facelets.tag.TagHandler;
> import com.sun.facelets.tag.jsf.ComponentConfig;
> import org.apache.myfaces.custom.aliasbean.AliasBean;
>
> import javax.el.ELException;
> import javax.faces.FacesException;
> import javax.faces.application.Application;
> import javax.faces.component.UIComponent;
> import javax.faces.webapp.UIComponentTag;
> import java.io.IOException;
>
> public class AliasBeanHandler extends TagHandler
> {
> private TagAttribute valueAttr;
> private TagAttribute aliasAttr;
>
> public AliasBeanHandler(ComponentConfig tagConfig)
> {
> super(tagConfig);
>
> valueAttr = getRequiredAttribute("value");
> aliasAttr = getRequiredAttribute("alias");
> }
>
>
> public void apply(FaceletContext ctx, UIComponent parent) throws
> IOException, FacesException, FaceletException, ELException
> {
> Application app = ctx.getFacesContext().getApplication();
>
> AliasBean aliasBean = new AliasBean();
>
> String value = valueAttr.getValue();
> if (UIComponentTag.isValueReference(value))
> {
> aliasBean.setValueBinding("value",
> app.createValueBinding(valueAttr.getValue()));
> }
> else
> {
> aliasBean.setValue(value);
> }
>
> String alias = aliasAttr.getValue();
> if (UIComponentTag.isValueReference(alias))
> {
> aliasBean.setValueBinding("alias",
> app.createValueBinding(aliasAttr.getValue()));
> }
> else
> {
> aliasBean.setAlias(alias);
> }
>
> parent.getChildren().add(aliasBean);
> }
> }
>
> Thanks!
> Ciao,
> Mario
>
>
Re: facelets taglib for tomahawk and sandbox
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> I went back and reread your facelets thread, and it does appear to be
> a good dynamic ui:include. Why not use ui:param instead of f:param?
> ui:param is already defined for facelets.
>
Thanks for the tip. I am not that familiar with facelets yet, at all
just 3 days :-(, I'll look into this to see if ui:param will do the
trick too.
Ciao,
Mario
Re: facelets taglib for tomahawk and sandbox
Posted by Mike Kienenberger <mk...@gmail.com>.
Hey Mario,
Thanks for keeping me honest :-)
You've been correcting a number of my misconceptions recently :-)
I went back and reread your facelets thread, and it does appear to be
a good dynamic ui:include. Why not use ui:param instead of f:param?
ui:param is already defined for facelets.
On 10/23/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> > For what it's worth, you're the first person in the history of
> > facelets to need it, at least as far as I've read on mailing lists.
> >
> Yep, sometimes I have some strange ideas .... :-)
>
> > Would it maybe be better to create a rendertime-compatible version of
> > ui:include tag?
> That is what I have posted on the facelets user ml. I just haven't had
> the time to look into a better way to pass down parameters to the include.
> It definitely will be possible I think, something like
> <ui:dynamicInclude page="">
> <f:param name="alias" value="#{backing}" />
> </ui:dynamicInclude>
> could be done (if it is what you meant), but I do not have the time yet
> to dig into this - hmmm ... when I think about it I feel it might be
> really easy. But then again, not yet - for now I'll stick with the
> aliasBean. The param way will be equally (un)flexible than the aliasBean
> yet - in fact - under the hood both will do the same.
>
> Ciao,
> Mario
>
>
Re: facelets taglib for tomahawk and sandbox
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> For what it's worth, you're the first person in the history of
> facelets to need it, at least as far as I've read on mailing lists.
>
Yep, sometimes I have some strange ideas .... :-)
> Would it maybe be better to create a rendertime-compatible version of
> ui:include tag?
That is what I have posted on the facelets user ml. I just haven't had
the time to look into a better way to pass down parameters to the include.
It definitely will be possible I think, something like
<ui:dynamicInclude page="">
<f:param name="alias" value="#{backing}" />
</ui:dynamicInclude>
could be done (if it is what you meant), but I do not have the time yet
to dig into this - hmmm ... when I think about it I feel it might be
really easy. But then again, not yet - for now I'll stick with the
aliasBean. The param way will be equally (un)flexible than the aliasBean
yet - in fact - under the hood both will do the same.
Ciao,
Mario
Re: facelets taglib for tomahawk and sandbox
Posted by Mike Kienenberger <mk...@gmail.com>.
Wow. No, I somehow missed the relevence of aliasBean on the facelets
mailing list.
For what it's worth, you're the first person in the history of
facelets to need it, at least as far as I've read on mailing lists.
Would it maybe be better to create a rendertime-compatible version of
ui:include tag? It seems like trying to mix aliasBean in the mix
will limit what you're able to do. Maybe that's what the component
you posted does, though.
On 10/23/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> > The reason that there is no alias bean handler is because it's not
> > needed with facelets.
> >
> Still, the tag is not working as it should, so providing a tag handler
> will fix this.
>
> > Instead you'd use a Facelets composition and ui:include statement.
> >
> That is not true for my use-case. As you might have seen on the facelets
> user list I have to play around with dynamic includes. Means, where a
> backing bean provides a path to an xhtml file to an include component
> which gets included at render time instead of compile time.
> This do not always work with compile-time includes.
> For example, an include embedded in an dataList or dataTable.
> For this you can't use the ui:include as it is evaluated at compile time
> - you probably know :-)
>
> I've posted a component which will include another xhtml parsed JSF view
> at render time on the facelets user list.
> So for these few places in our app I have to still go the aliasBean way.
>
> Ciao,
> Mario
>
>
Re: facelets taglib for tomahawk and sandbox
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> The reason that there is no alias bean handler is because it's not
> needed with facelets.
>
Still, the tag is not working as it should, so providing a tag handler
will fix this.
> Instead you'd use a Facelets composition and ui:include statement.
>
That is not true for my use-case. As you might have seen on the facelets
user list I have to play around with dynamic includes. Means, where a
backing bean provides a path to an xhtml file to an include component
which gets included at render time instead of compile time.
This do not always work with compile-time includes.
For example, an include embedded in an dataList or dataTable.
For this you can't use the ui:include as it is evaluated at compile time
- you probably know :-)
I've posted a component which will include another xhtml parsed JSF view
at render time on the facelets user list.
So for these few places in our app I have to still go the aliasBean way.
Ciao,
Mario
Re: facelets taglib for tomahawk and sandbox
Posted by Mike Kienenberger <mk...@gmail.com>.
Hey Mario,
The reason that there is no alias bean handler is because it's not
needed with facelets.
Instead you'd use a Facelets composition and ui:include statement.
On 10/23/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
>
> Please consider adding the following handler for the AliasBean to your
> project:
> (This is my first Tag-Handler, so I am not sure if there is a more
> elegant way - at least the AliasBean works here now)
>
> import com.sun.facelets.FaceletContext;
> import com.sun.facelets.FaceletException;
> import com.sun.facelets.tag.TagAttribute;
> import com.sun.facelets.tag.TagHandler;
> import com.sun.facelets.tag.jsf.ComponentConfig;
> import org.apache.myfaces.custom.aliasbean.AliasBean;
>
> import javax.el.ELException;
> import javax.faces.FacesException;
> import javax.faces.application.Application;
> import javax.faces.component.UIComponent;
> import javax.faces.webapp.UIComponentTag;
> import java.io.IOException;
>
> public class AliasBeanHandler extends TagHandler
> {
> private TagAttribute valueAttr;
> private TagAttribute aliasAttr;
>
> public AliasBeanHandler(ComponentConfig tagConfig)
> {
> super(tagConfig);
>
> valueAttr = getRequiredAttribute("value");
> aliasAttr = getRequiredAttribute("alias");
> }
>
>
> public void apply(FaceletContext ctx, UIComponent parent) throws
> IOException, FacesException, FaceletException, ELException
> {
> Application app = ctx.getFacesContext().getApplication();
>
> AliasBean aliasBean = new AliasBean();
>
> String value = valueAttr.getValue();
> if (UIComponentTag.isValueReference(value))
> {
> aliasBean.setValueBinding("value",
> app.createValueBinding(valueAttr.getValue()));
> }
> else
> {
> aliasBean.setValue(value);
> }
>
> String alias = aliasAttr.getValue();
> if (UIComponentTag.isValueReference(alias))
> {
> aliasBean.setValueBinding("alias",
> app.createValueBinding(aliasAttr.getValue()));
> }
> else
> {
> aliasBean.setAlias(alias);
> }
>
> parent.getChildren().add(aliasBean);
> }
> }
>
> Thanks!
> Ciao,
> Mario
>
>
Re: facelets taglib for tomahawk and sandbox
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
Please consider adding the following handler for the AliasBean to your
project:
(This is my first Tag-Handler, so I am not sure if there is a more
elegant way - at least the AliasBean works here now)
import com.sun.facelets.FaceletContext;
import com.sun.facelets.FaceletException;
import com.sun.facelets.tag.TagAttribute;
import com.sun.facelets.tag.TagHandler;
import com.sun.facelets.tag.jsf.ComponentConfig;
import org.apache.myfaces.custom.aliasbean.AliasBean;
import javax.el.ELException;
import javax.faces.FacesException;
import javax.faces.application.Application;
import javax.faces.component.UIComponent;
import javax.faces.webapp.UIComponentTag;
import java.io.IOException;
public class AliasBeanHandler extends TagHandler
{
private TagAttribute valueAttr;
private TagAttribute aliasAttr;
public AliasBeanHandler(ComponentConfig tagConfig)
{
super(tagConfig);
valueAttr = getRequiredAttribute("value");
aliasAttr = getRequiredAttribute("alias");
}
public void apply(FaceletContext ctx, UIComponent parent) throws
IOException, FacesException, FaceletException, ELException
{
Application app = ctx.getFacesContext().getApplication();
AliasBean aliasBean = new AliasBean();
String value = valueAttr.getValue();
if (UIComponentTag.isValueReference(value))
{
aliasBean.setValueBinding("value",
app.createValueBinding(valueAttr.getValue()));
}
else
{
aliasBean.setValue(value);
}
String alias = aliasAttr.getValue();
if (UIComponentTag.isValueReference(alias))
{
aliasBean.setValueBinding("alias",
app.createValueBinding(aliasAttr.getValue()));
}
else
{
aliasBean.setAlias(alias);
}
parent.getChildren().add(aliasBean);
}
}
Thanks!
Ciao,
Mario
Re: facelets taglib for tomahawk and sandbox
Posted by Sochor Zdeněk <zd...@ataco.cz>.
Hi,
a year ago i was playing with OLD generator to make it work again for
Tomahawk's core components - see
https://issues.apache.org/jira/browse/TOMAHAWK-819
- attachment tomahawk(no roleSelectionMode).patch
I withdrove the issue mainly because it become invalid in a matter of
weeks AND in that time it was
decided to switch to maven plug-in.
It was quite painful to make that patch due to heavy modifications in
components' getters and/or setters.
If part of that patch is locally applied (ONLY for xml definition
files), one can see almost all occurencies of unusual methods
which will have to be modified/extended during autogeneration (i
extended old generator for not rendering setter and/or getter).
I tried to complete as many missing attributes as i could, but i KNOW
that i missed a hell many of them in patch.
(mostly ones i sent patch for in
https://issues.apache.org/jira/browse/TOMAHAWK-955).
<https://issues.apache.org/jira/secure/attachment/12347078/tomahawk%28no+roleSelectionMode%29.patch>
I have to say i don't even slightly envy anyone who will try to port
Tomahawk to new generator. :D
I would help with that if that generator was able to be extended.
I really have issues with it in its current form e. g. magic comment
/**///methodName for not generating that method.
But it would be nice way how to ensure correctness of components and tags.
Regards,
Zdenek
Bruno Aranda napsal(a):
> I did start with the implementation of tomahawk using the faces plugin
> (not the old generator that Mario may be refering). The efforts are
> done in a tomahawk branch, but due to lack of time I haven't got the
> time to continue (I hope to do so :)). Configuring the
> maven-faces-plugin to do something, as Andrew has already experienced,
> is not the easiest thing in the world, but once the setup is done it
> works like a charm.
> MyFaces 1.2 Core uses the system, but of course it does not generate a
> taglib because the standard components are already covered by facelets
> taglibs itself.
>
> Cheers,
>
> Bruno
>
> On 22/10/2007, Andrew Robinson <an...@gmail.com> wrote:
>
>> MyFaces 1.2 core uses the Trinidad maven plugin (it wasn't me that did
>> that integration though). I don't see any taglib.xml files though, so
>> it doesn't look like it is configured to support facelets (which the
>> plug-in is capable of generating)
>>
>> -Andrew
>>
>> On 10/22/07, Mike Kienenberger <mk...@gmail.com> wrote:
>>
>>> On 10/22/07, Mario Ivankovits <ma...@ops.co.at> wrote:
>>>
>>>> If it takes years of getting tomahawk running again with the generator,
>>>> why do you think it will happen someone soon ;-) - sorry ;-)
>>>>
>>> Touche! :-)
>>>
>>> That's a fair response, but since someone (Andrew?) has gotten it
>>> working with MyFaces Core 1.2, I think it could happen soon with
>>> Tomahawk. :-)
>>>
>>> My biggest problem is a lack of time to learn Maven. I haven't even
>>> had time to work on a JSF project since May, although I'm hoping that
>>> will change again in the next month or two.
>>>
>>>
>
>
>
Re: facelets taglib for tomahawk and sandbox
Posted by Bruno Aranda <br...@gmail.com>.
I did start with the implementation of tomahawk using the faces plugin
(not the old generator that Mario may be refering). The efforts are
done in a tomahawk branch, but due to lack of time I haven't got the
time to continue (I hope to do so :)). Configuring the
maven-faces-plugin to do something, as Andrew has already experienced,
is not the easiest thing in the world, but once the setup is done it
works like a charm.
MyFaces 1.2 Core uses the system, but of course it does not generate a
taglib because the standard components are already covered by facelets
taglibs itself.
Cheers,
Bruno
On 22/10/2007, Andrew Robinson <an...@gmail.com> wrote:
> MyFaces 1.2 core uses the Trinidad maven plugin (it wasn't me that did
> that integration though). I don't see any taglib.xml files though, so
> it doesn't look like it is configured to support facelets (which the
> plug-in is capable of generating)
>
> -Andrew
>
> On 10/22/07, Mike Kienenberger <mk...@gmail.com> wrote:
> > On 10/22/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > > If it takes years of getting tomahawk running again with the generator,
> > > why do you think it will happen someone soon ;-) - sorry ;-)
> >
> > Touche! :-)
> >
> > That's a fair response, but since someone (Andrew?) has gotten it
> > working with MyFaces Core 1.2, I think it could happen soon with
> > Tomahawk. :-)
> >
> > My biggest problem is a lack of time to learn Maven. I haven't even
> > had time to work on a JSF project since May, although I'm hoping that
> > will change again in the next month or two.
> >
>
Re: facelets taglib for tomahawk and sandbox
Posted by Andrew Robinson <an...@gmail.com>.
MyFaces 1.2 core uses the Trinidad maven plugin (it wasn't me that did
that integration though). I don't see any taglib.xml files though, so
it doesn't look like it is configured to support facelets (which the
plug-in is capable of generating)
-Andrew
On 10/22/07, Mike Kienenberger <mk...@gmail.com> wrote:
> On 10/22/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > If it takes years of getting tomahawk running again with the generator,
> > why do you think it will happen someone soon ;-) - sorry ;-)
>
> Touche! :-)
>
> That's a fair response, but since someone (Andrew?) has gotten it
> working with MyFaces Core 1.2, I think it could happen soon with
> Tomahawk. :-)
>
> My biggest problem is a lack of time to learn Maven. I haven't even
> had time to work on a JSF project since May, although I'm hoping that
> will change again in the next month or two.
>
Re: facelets taglib for tomahawk and sandbox
Posted by Mike Kienenberger <mk...@gmail.com>.
On 10/22/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> If it takes years of getting tomahawk running again with the generator,
> why do you think it will happen someone soon ;-) - sorry ;-)
Touche! :-)
That's a fair response, but since someone (Andrew?) has gotten it
working with MyFaces Core 1.2, I think it could happen soon with
Tomahawk. :-)
My biggest problem is a lack of time to learn Maven. I haven't even
had time to work on a JSF project since May, although I'm hoping that
will change again in the next month or two.
Re: facelets taglib for tomahawk and sandbox
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> There are already "tomahawk-facelets.jar" files out there if you want
> to use something with drop-in support. See the wiki page for a link
> to Bruno's http://code.google.com/p/tomahawk-facelets project.
>
Thanks for the link!
> If three years of maintaining the file on the wiki hasn't been enough
> to catch all of the errors (with a large base of end-users who are
> able to modify the page)
Users are often not that enthusiastic to report back their changes ( I
think), especially if you spent hours to figure out whats going on. If
you are behind your timeframe you'll often "forget" to change the wiki -
your just happy that it works now.
Also some users are just too shy to change something in public, but it
is easy to file a jira or raise something on the ml, then a developer
will pick it up and change whats required.
> The component generator is already being used for Trinidad and MyFaces
> 1.2, if I'm not mistaken. Why not fix the problem correctly?
If it takes years of getting tomahawk running again with the generator,
why do you think it will happen someone soon ;-) - sorry ;-) - but
seriously, I have no knowledge with this issue - in fact, I am waiting
that someone will bring the generator online again :-(
ANYONE?
Ciao,
Mario
Re: facelets taglib for tomahawk and sandbox
Posted by Mike Kienenberger <mk...@gmail.com>.
There are already "tomahawk-facelets.jar" files out there if you want
to use something with drop-in support. See the wiki page for a link
to Bruno's http://code.google.com/p/tomahawk-facelets project.
I'm still -1 on any hand-maintained facelets taglib.xml being put
directly into the Tomahawk jar since once you go this route, it
becomes impossible to fix an error without recompiling MyFaces
Tomahawk or manually hacking up the jar file, and -- as you pointed
out -- there are still likely errors in the wiki page. Someone just
corrected the schedule component a few days ago. I don't have a
problem with putting hand-maintained changes in another integration
jar, like was done for http://code.google.com/p/tomahawk-facelets
If three years of maintaining the file on the wiki hasn't been enough
to catch all of the errors (with a large base of end-users who are
able to modify the page), why do you think that restricting the
correction of errors to MyFace committers is going to be an
improvement? Most of the wiki page corrections and additions have
been made by non-committers.
The component generator is already being used for Trinidad and MyFaces
1.2, if I'm not mistaken. Why not fix the problem correctly?
On 10/22/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
>
> I know, this has been discussed in lengthy already, but I'd like to warm
> it up again.
>
> I'd like to add the facelets taglib and tag-handler one can find all
> around the net to our myfaces libs.
> I found this a REAL pain to figure out all the required stuff to get
> tomahawk and the sandbox running again with facelets - every newbe will
> be lost, there are other problems one should solve and not to such
> trivial stuff which requires a lot of searching.
>
> I know, we have a wiki for this, but as far as I can see this is not
> really maintained. And it is hard to maintain, we (I think I can write
> WE here, sorry if not) developers prefer to work with svn and not with
> any wiki page where you even can't be sure if the stuff compiles - and
> it is much harder to remember the wiki page than lookup the resource in
> your ide and fix some stuff.
> I think the argument that only a component generator is safe enough to
> create the taglib is not valid, if there are errors in the taglib or one
> of its handler class they will uncover sooner or later, in the end, we
> have a fully working drop-in-able tomahawk and sandbox stuff.
>
> PLEASE, lets go that way!!
>
> Ciao,
> Mario
>
>