igor.vaynberg wrote:
>
> you cant because it wont have any markup to attach to, instead you can
> simply output the messages yourself, see my reply to this thread:
>
Thanks a lot Igor
However, I'm a bit upset not to be able to use other components in a
Behavior, it kind of breaks the Wicket way of doing things.
Thinking about that, I was wondering whether it would be possible to have
Behavior with markup attached working this way, let's called it "composer" :
<wicket:composer>normal html or wicket
components<wicket:composedComponent>normal html or wicket components
</wicket:composer>
The idea is to be able to "enrich" a component through the "composer" (or
whatever name is best suited) : the component whom the composer is added
would be surrounded by the content of the wicket:composer component (be it
html or components). It would avoid the use of
component.getResponse().write(XX) and allow the use of components.
For sure it might not be perfect, for example multiple composers on the same
"composedComponent" might be tricky, but overall, what do you think of the
idea ?
++
zedros
--
View this message in context:
http://www.nabble.com/How-to-add-a-component-in-a-behavior---tp21758993p21820319.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
