Hasn't anybody else been in this situation ? I finally checked it is
necessary for a regular tag with a wicket:message attribute and with wicket
component childs to be also a wicket component... Maybe it would be nice to
have this information on the wiki page talking about the wicket:message
wicket:message is not intended to be used on actual wicket components,
only on raw markup. if you have a component then its trivial to add
the localized attribute from code. remember, wicket prefers everything
to be done from code. wicket:message exists because creating a markup
container in code
Oh, now I think I got your point... I don't know how wicket treats markup
internally, I could expect some markup substitution on the attribute
wicket:message='summary:myResource' by summary='This table'
In fact, I have tried using another tag, without any child Wicket Component
input
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
when you have markup like:
table wicket:message=summary:myresource
trtdspan wicket:id=myComponent/span/td/tr
/table
where do you expect your localized message to go?
-igor
On Wed, Apr 28, 2010 at 2:51 AM, Xavier López xavil...@gmail.com wrote:
Hi,
I have just bumped into a particular
Hi, I'd expect it to lie in the ContainerComponent's folder, assuming
ContainerComponent is the the Page or Panel associated with that markup...
In other words, getString(myresource) from that component would find it.
Does this have something to do with that error ?
Thanks,
Xavier
2010/4/28
i meant where do you expect the localized message to be rendered into?
if wicket:message is attached to the table tag?
-igor
On Wed, Apr 28, 2010 at 9:52 AM, Xavier López xavil...@gmail.com wrote:
Hi, I'd expect it to lie in the ContainerComponent's folder, assuming
ContainerComponent is the
