John Carlson-5 wrote:
>
> I have had several pages that will not initially load the wicket-ajax
> functionality. [...] I did alittle snooping and found that on the first
> load
> wicket doesn't add the wicket-ajax.js to the markup.
>
You should try the header contributor. Example:
public somecomponent (String myid) {
super (myid);
add (HeaderContributor.forJavaScript(somecomponent.class,
"javascriptfile.js"));
...
}
John Carlson-5 wrote:
>
> I setoutputmarkupid(true) on all the related things as far I can tell.
> Does the order of setting markup Id and adding things to the page
> matter? ie.
>
setOutputMarkupId is needed to enable wicket to update a
component after requests are returned to the client. It has no
effect here.
--
View this message in context:
http://www.nabble.com/wicket-ajax.js-not-added-tf4512483.html#a12878783
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
