-
1. Re: What is the Best-Practice strategy on employing a single jQuery library (and version) with RF?
bleathem Nov 20, 2013 12:41 PM (in response to feder)In RichFaces 4.3 you would use:
<h:outputScript name="jquery.js" />
-
2. Re: What is the Best-Practice strategy on employing a single jQuery library (and version) with RF?
feder Nov 21, 2013 8:02 AM (in response to bleathem)Brian,
Just to get this straigt for me and others:
- <h:outputScript name="jquery.js" /> should be the path to the RF jquery, right?
- RF will NOT output another script tag with jquery.js into the head tag, when using <h:outputScript name="jquery.js" /> and the user requests a page which includes a a4j or rich tag?
Can these questions be answered with yes?
Thanks for the clarification,
Feder
-
3. Re: Re: What is the Best-Practice strategy on employing a single jQuery library (and version) with RF?
bleathem Nov 22, 2013 5:55 PM (in response to feder)1. <h:outputScript name="jquery.js" /> should be the path to the RF jquery, right?
No. h:outputScript uses the JSF resource library/name syntax. The above is telling JSF to output the script named "jquery.js" in the library "" as bundled in the RichFaces jar. (In RichFaces 4.5/5 we are moving this script into a non-empty library).
2. RF will NOT output another script tag with jquery.js into the head tag, when using <h:outputScript name="jquery.js" /> and the user requests a page which includes a a4j or rich tag?
Correct. JSF resources are included only once on a page. This is why I recommend using the h:outputScript tag, rather than linking the file directly.