Ganesh schrieb:
Hi Werner,
There are some corners within the ajax response XML format that doesn't
make much sense for me in respect to JSF. Especially for the insert,
delete and attributes sections of the update element I cannot see how to
trigger them from the existing jsf.ajax.request interface. Still they
must be implemented because they make part of the spec and I'm thankful
that you are taking on these hard-to-test tasks.
Actually I have to recheck the entire java part especially the JavaDocs
(have in mind the about half of the specs functionality is documented in
the javadocs instead of the PDF)
if there are cases where the deletes and inserts can be triggered from
within the components automatically.
My personal guess is that this stuff is a handful of shortcuts for the
component writers so that they can gain some additional functionality
easily which would be hard to deal without.
After all within the context of a classical response writer api
the inserts and deletes are hard to process but sometimes you need them.
I´d rather have a protocol which is more extensive in this area than
having a few missing parts which then cannot really be added!
But I haven´t been too much concerned with the java side of the jsf spec
for now because I usually focus on one area before going into the next!
So I am not sure if I have missed something there!
The jira task on the extensions (MYFACES-2174) is NOT for the visual
part. The visual part (disable components and show loading bar during
request) would truely make a good extension, but I've set this aside
until the core is fully functional. The jira is for the addional
attributes for the xhr core: pps, queuesize and errorlevel.
Ok thanks for the clarification.
Werner
