On 3/10/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > No one? > > I just want to collect what should be done to make shared clean: > > > > I think the following should be moved to tomahawk: > > > > JavascriptUtils > > DummyForm* > > MyfacesConfig > > > > What else? > > > > I see a problem with moving DummyForm out, though, it cant stay there. > > Actually the dummyForm stuff works with the h:command* tags, if we move > them to tomahawk (or the new commons) we have to move the necessary code > out of shared and then the h:command* tags loose this functionality. > They provide some methods to overload to be able to implement it again, > though. > > Without any further action only the t:command* counterparts are able to > initiate a dummyForm. IMHO this is how it should be, but, some > applications out there stop working.
Hmmm. There are actually two questions to solve: * should we move DummyForm to tomahawk at all? * when should we move it? If the answer to the first question is "yes" the answer to the latter must be: "now - the sooner the better" My feeling is that we should do it and upon releasing tell the users why we did it. We might break some users apps, but we have a good point: The user's app won't run on any other JSF impl anyway. If we decide to leave the feature in impl (and at least make it optional via config param), we should schedule it for addition to the future commons project. And we must solve the "fully qualified names"-String problem first, of course. > Shall we tell the user to change those links to t:command* tags, or are > we willing to provide overloaded renderers through > tomahawk/faces-config.xml? Yes, that would be the consequence of the move. > The latter again is error prone, as then it is very likely to run in the > "order of faces-config.xml processing" problem and our renderer might > mask or might be masked by another one. Well, this is always a problem. Also when the feature stays in impl. Or do I miss something? Manfred
