Yes, you are right, Wilhelmsen, and that's what Wicket is doing, I understand that correctly. The problem is, when I have a wicket component attached to that <table> tag. Wicket seems to treat that <table> as a component, with autogenerated wicket:id, and logically, expects the child components (in markup) to be added to it. I suppose I have to manually model that <table> into a wicket component (i.e. WebMarkupContainer) in order to be able to add those child components to it and let Wicket process the component hierarchy correctly...
BTW, I just noticed I wrote the last message incorrectly: <input type="text" wicket:message="title:myresource"></input> Turns into <input type="text" title="Test Title"></input> Thanks, Xavier 2010/4/29 Wilhelmsen Tor Iver <[email protected]> > > i meant where do you expect the localized message to be rendered into? > > if wicket:message is attached to the table tag? > > Well, since he is using the attribute version of wicket:message, I guess he > expects the output from > > > >> <table wicket:message="summary:myresource"> > > to be > > <table summary="localized message with key myresource"> > > - Tor Iver > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
