Martijn Dashorst wrote: > > Where the fragment is defined is different from where it is used. You > define the fragment outside the form (just as you would do a panel, > but that is in another file). The fragment is then instantiated and > added to the place where it will render itself, in your case: the > form. >
Well, if I put the fragment outside the form "form:markupId" makes sense. So it seems like markupId must always be the full path from the form. -- View this message in context: http://www.nabble.com/using-fragment-inside-of-form-tf3486450.html#a9734913 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
