> Though if you look at that: it's between <wicket:head> tags, meaning > it will be contributed to the header. What the resolver for that tag > will do is try to resolve it to a package resource at run time, so > <link wicket:id="css" rel="Stylesheet" type="text/css" href="tree.css" > /> will be expanded to <link rel="stylesheet" type="text/css" > href="/wicket-examples/nested/resources/wicket.markup.html.tree.Tr > ee/tree.css" > />. > > Did you have a problem, or did you expect to have one?
Well, since the code has changed and there is no more <wicket:head> in the tree component, discussion of the problem I was having is moot... but to answer your question, the problem was having two components with the name "css". Since "css" is a rather common name to use for a CSS comonent, the chances of conflict are high. Since in my border, I also named my CSS component "css", Wicket threw an exception. Cheers, Dave ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
