Hi Cagatay! > Since not the form component itself but mainly the renderer is going > to be extended and refer to the original form renderer after doing > some script rendering, I guess t:form should work with RI as well. The sandbox form renderer do not use delegation, but uses inheritance. This means that the tomahawk form uses the MyFaces form render "engine" then. There is nothing bad with this, if our form renderer behaves in a RI compatible way, but .... is this the case? Previously I was told (from the users) that this is NOT the case for the command* guys, and this might also be true for our form too - I wonder why Martin didn't respond to this topic? Hey - Martin, whats up?? ;-)
I already realized that we want the move to tomahawk to allow your validation stuff ;-), but this also means that this validation stuff requires the use of t:form what a JSF-RI user cant do. So all this new and sexy stuff cant be used by this group. Remember, tomahawk should be a component library and should work in any JSF compatible environment, at least that was our goal. To sum up my point: * Its nothing bad to move now and document its "not compatible to RI" * But, as soon as possible we should have a look at making form/command* RI compatible However, Cagatay, can't we play a little bit longer in the sandbox with your stuff and also the clientConverter thingy? Maybe in the meantime we find some volunteer for the problem above. At least one who can check the s:form in a JSF-RI environment would be very nice. Ciao, Mario
