Matthias Wessendorf schrieb:
> On Fri, Apr 17, 2009 at 12:41 PM, Ganesh <gan...@j4fry.org> wrote:
>> Hi,
>>
>> Here's a question concerning the extension parameters pps, queuesize and
>> errorlevel in conjunction with the f:ajax tag. They form part of the
>> Javascript xhrCore and can be set via jsf.ajax.request(this, event,
>> {execute:'xxx', render:'yyy', myfaces:{pps:true, queuesize:1, errorlevel:
>> 'error'}}).
>>
>> For the ajax tag the extension parameters could reside in an attribute
>> myfaces: myfaces="{pps:true, queuesize:1, errorlevel: 'error'}".
>>
>> Now, should this extension parameter become part of the f:ajax tag or should
>
> mf:ajax ?
> By that one could use this "core extension", when using myfaces lib.
>
>
>> we build a t:ajax tomahawk tag?
>
> -1 this would tie the use really to tomahawk;
> Why not doing a mf:ajax which is a taglib that sits inside the
> myfaces-impl.jar
But then any web page that uses this mf:ajax tag would not work when run
on a different container (eg mojarra), as that tag would not exist.
The tomahawk tag sounds better to me. If I understand correctly, a page
using it would still work on other containers as long as tomahawk was in
the classpath. The extra params to jsf.ajax.request would be rendered
into the page, and sent back to the container, but then not used.
Possibly nested attributes could be used?
<f:ajax ...>
<f:attribute name="myfaces:pps" value="true"/>
<f:attribute name="myfaces:queuesize" value="1"/>
</f:ajax>
When a page containing that tag is used in a container that doesn't
recognise these attributes, I expect they would just be ignored (the
extra attributes would not be rendered into the generated page).
Regards,
Simon
