I can appreciate what it currently does - I just think it could be a little more convenient.
It would still provide the default behavior, but allow keys to be translated with the child scope primarily - in the same way it allows visibility to be driven with the child scope. Thanks for your feedback Igor. igor.vaynberg wrote: > > i do not think this is the irght way to go. the nesting is: > > <wicket:panel> > <wicket:enclosure child="productsListView"> > <wicket:message key="name"/></th></tr> > > so clearly the key is owned by the panel. these are the rules for > wicket:message. keep in mind the tag is a convinience and so we try to > keep it as simple as possible. you can always add a label that uses > whatever you want as the localizer. > > -igor > -- View this message in context: http://www.nabble.com/Question-re-wicket%3Aenclosure-tag-and-resource-resolution-with-wicket%3Amessage-tags-tp21008465p21023555.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]
