Interesting how the HeaderResponseFilteredResponseContainer in this 
example is after the </body> tag even though best practices as well as the 
Javadoc suggest it should be just before the </body>.  Perhaps the example 
should be changed so as not to set a bad...er...example...

A header response that creates two buckets. The header bucket will contain 
all references to CSS. The other bucket will contain all Javascript, and 
you will need to add a HeaderResponseFilteredResponseContainer to the 
footer of your page (typically just before the end body tag) to render the 
Javascript. 





From:   Martin Grigorov <mgrigo...@apache.org>
To:     users@wicket.apache.org
Date:   02/13/2011 01:51 PM
Subject:        Re: usage of JavascriptFilteredIntoFooterHeaderResponse



Another good example is
http://www.wicket-library.com/wicket-examples/resourceaggregation

This example application is only in 1.5 but it can be easily 'translated' 
to
1.4.

On Sun, Feb 13, 2011 at 7:09 PM, Zilvinas Vilutis <cika...@gmail.com> 
wrote:

>
> Thank you! That's what I needed!
>
> -----
> --------------------
> nothing is impossible
> --
> View this message in context:
> 
http://apache-wicket.1842946.n4.nabble.com/usage-of-JavascriptFilteredIntoFooterHeaderResponse-tp3302046p3303816.html

> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>





Notice: This communication, including any attachments, is intended solely 
for the use of the individual or entity to which it is addressed. This 
communication may contain information that is protected from disclosure 
under State and/or Federal law. Please notify the sender immediately if 
you have received this communication in error and delete this email from 
your system. If you are not the intended recipient, you are requested not 
to disclose, copy, distribute or take any action in reliance on the 
contents of this information.

Reply via email to