Ok guys to get back to the topic, I now have committed the clean parts
of the renderer and the behavior so someone else can take over from now.
All which is missing is the full tag integration, I have not yet checked
the already existing tag code so I am not sure what is missing there.
Btw. Simon... you had in your comments on the behavior class
that the delta state saving needs to be added, it is added now.
I cross ported our state helper to the beavior class.
There were limits in the API which prevented to reuse the existing one.
Maybe we can move the code over to impl, so that we can unify it under
a custom impl interface.
In short sorry for the code duplication but this needs to be fixed in
spec level in a clean manner.
Werner
Werner Punz schrieb:
Ok I have a rather difficult question here:
I did the f:ajax part of the behavior and the renderer clean room.
But to get it up and running under a testing ground fast meant
I had to check the f:ajax taghandler from mojarra and patch 2-3 things
in, which was triggering my tag instead of the mojarra one.
The main reason I am asking here is I am in the middle of a
reimplementation of the said tag handler.
But I am sort of stained by the mojarra sources, by having seen that part.
My question is now. The ajax tag code is clean and the renderer as well,
but the tag handler is not. Shall I stop working on it and let someone
else do it, or shall I continue?
The tag handler is a complete reimplementation however and has severe
structural differences, there is not a single line of code not written
by me, but as I said ... stained due to having patched mojarras code for
testing :-(.
