I need to look into a bit more. I way out-of-order for some days.
Juergen On 5/28/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Ah, yes. I missed that one. Just came back from a vacation :) Eelco On 5/28/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > AlMaw also already looked at it: > http://www.nabble.com/Chaining-IComponentResolvers-tf3803758.html#a10763056 > > is juergen around? > > johan > > > On 5/28/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > Not sure whether someone was already looking at this, but currently > > org.apache.wicket.markup.html.basic.SimplePageTest#testRenderHomePage_7 > > is failing. The problem is that > > > > <input type="image" src="test.gif" > > wicket:message="attr-name:i18n-key">test 2</input> > > > > is resolved by WicketMessageTagHandler and thus not by > > RelativePathPrefixHandler. > > > > I'm not sure what the best solution is to this, but my first question > > is whether it is really a good idea to create auto components for all > > the tags we find that need to have the relative path fix in the first > > place. I understand we need to do this dynamically because of URL > > mounting and stuff, but can't we use for instance IResponseFilters for > > this problem instead? > > > > If I didn't overlook something, and the above thought is correct, the > > same goes for wicket:message tags. Do they really need to be resolved > > to components? I'm afraid those auto components can add up quite a bit > > when it comes to memory usage. > > > > WDYT? > > > > Eelco > > >
