Hi Hendrik I am very sorry for that - but it is unfortunately as it is, at least according to my knowledge. Maybe I am telling you rubbish, you should also contact the JSF reference implementation people on their mailing list and please tell back what you hear there if they know of any remedy.
One way of going around that I would have - what about using the "forceId" attribute that all the MyFaces extended standard components provide (and the custom components should provide)? If you keep yourself to unique ids, this would be a viable solution. regards, Martin On 5/20/05, Hendrik Neumann <[EMAIL PROTECTED]> wrote: > Martin, > > please tell me, that you're kidding! I simply can not believe that Sun > Microsystems passes a spec which bashes offical web-standards! What is about > MathML, SVG and so on: they need a valid XML-file to work, which JSF > apparently is not creating. This simply means that all new and modern > HTML-extensions which should be established with XHTML are not possible with > JSF, because the spec defines invalid XML-documents which forces me as a > developer to use HTML4 from 1999. And this means that the JSF-spec is only > practical for dinky "Hello World"-web-apps without any forward-looking > techniques... > > I simply can not believe this... JSF forces me to use outdated standards and > techniques... this is simply harrowing! > > Isn't it possible to develop my own ID-Generators or such a thing? Or is it > possible to tell the web-browsers that they shouldn't take care about wrong > ids? Or a Java-Script which replaces the invalid IDs? I had already tried to > set manually id-names which solves the problems for a few moments but after a > few clicks on the pages, my own ids are extended in the invalid way with the > ":" and "_"-characters and the web-browser refuses to show my pages. This > small id-disfigurement makes JSF in fact unusable to me if there really isn't > a workaround... > > Regards, > Hendrik > > P.S: Of course this email IS NOT aimed against you MyFaces-guys - you have > done a great work, thank you very much for this (nevervethless it seems that > jsf was the wrong spec for my project)! >
