So the other option would be to use component resolvers. Which like you said would only work for tags with wicket:id/ wicket:foo. Would it be hard to change the parsing process so that tags with wicket:message will be read as ComponentTag, even if they are not part of <wicket:foo or have wicket:id in them?
Eelco On 9/18/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > I don't think that'll work. Remember the markup for a panel gets > > loaded only once no matter how often and where else the Panel is used. > > The component path is only true for the component which initially > > loads the markup but it is most likey wrong for all other panels of > > the same type. > > It needs to be done just once for every locale/ variant; after that > the cached markup is reused with the altered attributes, right? > > 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
