its not that it isnt "smart"...the problem here is that wicket:head and iheadercontributor are two disjointed concepts, even though it kinda looks like they do the same thing. all that wicket:head does is collect markup and stick it into the head element, it doesnt know whats inside - its just a string.
perhaps the jquery guys should make their stuff a little more flexible...maybe if you do this page.setmetadata(new jquery.includedKey(), true); their header contributor would omit the inclusion of the jquery.js. given that is a workaround, and a more general solution would be nicer...but that will take quiet some thinking. feel free to add a jira issue so we can keep track whenever one of us thinks of something clever/elegant for this. -igor On Feb 1, 2008 2:08 PM, Edvin Syse <[EMAIL PROTECTED]> wrote: > > if you put the reference to jquery into wicket:head of the base page > > will it load before or after? then put only your initialization code > > into a header contributor. > > -igor > > That works up until you use wicketstuff-jquery in your app. Then JQuery is > loaded via a headercontributor, and you end up loading two > versions of jquery, which crashes your page :( > > I have tried to load jquery via <wicket:head> in the same way it is added via > the headercontributor (path to resources/blablabla), but > wicket doesn't "detect" it, and adds both the jquery from the > wicketstuff-jquery-behaviour and the manual one.. > > If the <wicket:head> renderer was "smart enough" to detect that the same file > was added via a headercontributor I would be in business, but > it doesn't :( > > > -- Edvin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
