Hi Leandro, Yes this is a known problem. The JSF specification states (or was stating) that facelet-taglibs should only be recognized and used if they define a version attribute which is set to "2.0" (so you need <facelet-taglib version="2.0"> to make this work).
After many discussions about that, a decision was made to get rid of this (stupid) check. So this should be in place in the next (beta) release of myfaces. If you want to try it out now, you could use one of the latest nightly builds or simply add the version attribute in your facelet-taglib. Regards, Jakob 2010/3/6 Leandro de Oliveira <[email protected]> > Hi, > > I've submitted this bug on mojarra bug tracker: > https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1445 > > Then, I've decided to try it on myfaces, so I just commented out jsf-api > and jsf-impl and added myfaces-api and myfaces-impl in my pom.xml. > > The url working.jsf worked as expected in both implementations. But myfaces > simply didn't resolve this line in not-working.xhtml: > > <issue:mycomp color="#dddddd" /> > > Other tags (h:head, h:body) resolved correctly. > > Is this a bug in myfaces too? > > Thanks > > > > > ____________________________________________________________________________________ > Veja quais são os assuntos do momento no Yahoo! +Buscados > http://br.maisbuscados.yahoo.com >
