Hi, Unlike JSP tags, facelet tags do not declare or validate attributes (ie you can define any attributes you like on a facelet tag without getting a "this attribute does not exist" error) [1], so the TCK presumably would not be able to detect whether MyFaces has extended the spec with custom attributes.
However my personal opinion is that adding custom behaviour to a standard tag is *wrong* if the app would fail to work correctly when the attributes are ignored. In other words, adding "optimisation" or "debugging-helper" params is acceptable, but otherwise not. Adding behaviour-changing features to standard tags is setting a portability trap for users, where their app will silently fail to run correctly when executed on a different JSF implementation. That seems unacceptable to me, even if the TCK cannot technically detect it. So for the two params you are proposing which are just performance tweaks, just attributes on f:ajax, or using nested f:attribute seems ok. But for the other one (queueLength?) I would strongly recommend an mf:ajax or mf:attribute tag be created. [1] At least, facelets for JSF1.2 works this way. I presume this hasn't changed... Regards, Simon Ganesh schrieb: > Hi Werner, > > Does this mean Matthias succeeded in convincing you that f:ajax is > facelets-only and can receive an additional attribute without breaking > the TCK or the spec? > > Also, please see the spec, section 10.1: >>New features introduced in > version 2 and later are only exposed to page authors using Facelets. JSP > is retained for backwards compatibility.<< Imho, this is the polite way > of saying "JSP is dead". > > Best Regards, > Ganesh > > Werner Punz schrieb: >> Ok I did a quick look over the facelets section as it seems, it is >> facelets or jsp just like we had in the past... >> >> I would have loved to have a templating on the renderer side for jsp >> as well, oh well... >> >> Werner >
