Bordered pages (pages which have a Border child component and when you add child to the page you actually add it to the border) are always causing problems and are requiring special treatment in some disparate places in core. With 2.0 where we are trying to find the markup in the constructor it becomes even more difficult. Lets say the components id is "label", and the borders id is "border", than the markup path is "border:label", but the component path, as added to the page and not the border is "label". How should we figure out that we need to prepend an extra "border:"? Since we have markup inheritance now for quite a while there doesn't seem to be a use case for bordered pages anymore and because of the troubles with it I'd like to remove that feature from 2.0. Any objections?
Juergen ------------------------------------------------------------------------- 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
