> hmm but how do you get access to the enclosure object? it is only defined in > the parent. do you mean you would do > componentInsideEnclosure().getParent() ? > > i personally dont, but some people might do, component.getParent() and > expect a certain parent - but the enclosure is inserted in the markup only > so its invisible in the java component hierarchy - might be a bit confusiing > i suppose.
actually that was a bit tricky. I first tried that approach but because transparent containers such as "body" etc it was tricky and hacky. I'm now using a IMarkupFilter which kind of pre-reads the markup if <wicket:enclosure> without child attribute is found and determines the child id (if required). Thus when the markup gets rendered the name of the child component is always known. No problems with parents and transparent resolvers etc. I'll commit it in a minute 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
