> that wont work, some components such as <wicket:link> and <wicket:message> > only exist in markup
Igor, thank you for your answer. >From api doc: wicket:message="value=key" would replace or add the attribute "value" with the message associated with "key". I would expect it is implemented using AttributeModifier, not component. With wicket:link example you are right, but can be solved (you would have to add the component in code (or do some magic). Can you please give me other examples as well - I'm a bit curious and would like to find out if it is really impossible. Thanks saki > > -igor > > > On 11/3/06, Petr Sakar <[EMAIL PROTECTED]> wrote: >> >> Question / Idea: >> If I undestand it correctly, currently component hierarchy is build >> based >> on markup. How about to do it other way round ? For component hierarchy >> created in your java code lookup the markup ? >> >> saki >> >> >
