Matthias Wessendorf schrieb: > On Fri, Apr 17, 2009 at 2:24 PM, Ganesh <gan...@j4fry.org> wrote: >> >> As Simon said, inclusion into f:ajax is probably not a good idea, because >> applications using JSP+Mojarra would break when containing the additional >> param.
Just FYI, myfaces core *must* pass the Sun TCK (compatibility test kit) in order to call itself "JSF" at all. And the TCK specifically checks for non-standard attributes on any standard tags/classes. So adding any non-standard attributes to standard tags (eg adding stuff to f:ajax) simply cannot be done; the TCK will fail. Sun's intention is to specifically catch cases where a vendor has "non-standard" extensions that make pages non-portable to other implementations - like when Microsoft tried to extend Java with windows-only features. And this is a good thing IMO. Non-portable extensions have to go into separate libs instead. >From your description of the new flags, it sounds like a page will "fall back gracefully" when run on other containers (slightly noisier with JSF error messages, slightly more data posted on each submit, but still working) so nesting f:attributes seems fair in this case. One thing to check would be that the f:ajax tag isn't marked as "empty" in the DTD/schema, ie that f:attribute tags can be nested inside it. Cheers, Simon
