Ok, I really expressed my idea the wrong way with this. Don't get me wrong guys, I didn't intend to say that your rendering was not complex, or that I could override it all with little programming. Call this "Rendering" was actually unhappy, as you point out.
What I was saying is that I could override a specific thing (the generation of markup Ids, in this case). But if I look for a place to do that I found it con the very Component class, leaving me with only 2 choices: * Change Component itself and rebuild the jar: not desirable for obvious reasons. * subclass Component: not desirable because it means also subclassing every component class under Component. That was my analogy with struts where there is no way to customize specific parts of the building pieces (Actions, Forms, the RequestProcessor) without subclassing the whole thing. Matej Knopp-2 wrote: > > Our rendering is "little" more complicated than that. Also the markup > id assignment is not really part of rendering process, it takes place > sooner. There are technical reasons why it is not possible to preserve > markup id for components with setOutputMarkupId(true). It's been > discussed before. > -- View this message in context: http://www.nabble.com/Start-delegating-stuff-out-of-Component--tp15884385p15891158.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
