Hi, no specific reason I think. So far nobody ask for it with a good use case. I think it's ok to change the order.
-Juergen On Mon, Jan 30, 2012 at 9:13 AM, Martin Grigorov <[email protected]> wrote: > Hi, > > What is the reason the (more static, auto) ComponentTag's behaviors to > be executed *after* the (more dynamic, user supplied) Component's > behaviors ? > See org.apache.wicket.Component#renderComponentTag(ComponentTag). > > ComponentTag behaviors are usually added in IMarkupFilters (see > org.apache.wicket.markup.parser.filter.RelativePathPrefixHandler#onComponentTag > and > org.apache.wicket.markup.parser.filter.WicketMessageTagHandler#onComponentTag) > but those are not override-able by user-supplied behaviors because of > the order in Component#renderComponentTag(ComponentTag). > > The use case is: wicket:message="title:titleKey" should be used most > of the time but in some case the developer wanted to use a dynamic > title attribute with AttributeModifier.replace("title", > dynamicTitleModel) > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com
