Igor Vaynberg wrote:
icomponentresolver does exactly what its javadoc says - match markup
tags to components. if you want you can create those components on the
fly - but remember that this happens at render time so it might have
some side effects for you.
The javadoc mentions "component na
icomponentresolver does exactly what its javadoc says - match markup
tags to components. if you want you can create those components on the
fly - but remember that this happens at render time so it might have
some side effects for you.
you dont need to rewrite your panel as a component resolver an
Hello,
I have developed a panel named AutoComponentPanel that automatically adds wicket components based on (dynamic) markup. Looking at IComponentResolver I noticed some similarities. Can someone explain this class and its uses to me? Is it
something that I should want to use for AutoComponentP
I was looking at the code of AutoComponentPanel and found similarities
between this and IComponentResolver. AutoComponentPanel has an
overridable getMarkupComponent(ComponentTag, MarkupStream) where
IComponentResolver has resolve(MarkupContainer, MarkupStream,
ComponentTag). Can someone explain
