I was thinking more that I would just extend standard TextArea and TextField
components but override onComponentTag to replace whatever tagName was
supplied by the HTML monkey. So Wicket would continue doing its good stuff
but I wouldn't need two different HTML fragments or placeholder
oncomponenttag() is fine for extension, thats what it is there for. im
sure if someone made a good usecase for opening up passwordtextbox or
listchoice we would remove final.
-igor
On Jan 22, 2008 1:14 AM, Sam Hough [EMAIL PROTECTED] wrote:
I was thinking more that I would just extend
@Override
protected final void onComponentTag(final ComponentTag tag) {
tag.setName(input);
tag.put(type, text);
super.onComponentTag(tag);
}
Seems to do what I want but is this a valid extension point? In
PasswordTextBox and
its not that simple
input tag has no body input/ why textarea does textarea/textarea
also input stores its value in the value attr, textarea does it in its
body
that is why we have two separate components for this. you can of
course write your own that handles both cases properly...
-igor
