> WicketMessageTaghandler didn't need (I didn't look at the new code > yet) to know the component and the stack yet, as the properties were > assumed to be either in the corresponding properties file or the apps > properties file. Which is properly the limitation Eelco was talking > about.
Yeah, that's the limitation I'm talking about. So <wicket:message> has a full search stack while <foo wicket:message...> has not. I got around that by finding the proper component by doing a lookup through the component path, which I think should always succeed, as the call to create the container info (where the path is stored) and the call to WicketMessageTaghandler happens in the same request. It's a bit hackish, but it seems to work and doesn't break the API. Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
