Yeah, but a good framework should not get in the way of what you are trying to do, right? I spent 2-3 hours trying to figure out a way to do this with fragments :) Others will probably hit the same wall someday. Panels did work for my solution, but in this situation loading fragments as a "standalone component" would have been a more elegant solution for me.
I don't think the Wicket framework gets into your way. None of the fragment related sources are statically bound to Wicket. They are all registered or configured. Nothing prevents you from implementing your own component which does exactly that. Wicket is very flexible and customizable. It is just not available out-of-the box and yes implementing this component will require a little bit more insight than many users have.
Aaron
------------------------------------------------------- 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&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
