JSF: Why prependId = false in a form?

up vote2down votefavorite 1	I know what prependId=false does. It set the flag so that the id of the form does not prepend the id of the form child, but why? any particular reason why you do or dont want to prepend id? jsf link|improve this question asked Oct 19 '10 at 20:51 Thang Pham 2,32654099 82% accept rate
	feedback

5 Answers

activeoldestvotes

up vote8down voteaccepted

In my experience, I never use this attribute. However, in some cases it can be useful. When you use Facelets, you can create templates or include pages inside another page. So you can imagine that a page could be included in several different pages. Take the example where the parent pages contain a form, with different id: Page 1: id="form1">     src="pages/my-page.xhtml"/>     ... Page 2: id="form2">     src="pages/my-page.xhtml"/>     ... Now, in the my-page.xhtml, you have a . In the first case, the real ID of the input will be form1:foo, while in the second case, it will be form2:foo. This could create complex situations if you need a direct access to this component in Javascript or in Java (usingfindComponent("...") method). If you use prependId="false" (or on some components forceId="true"), the real ID will be simply foo, and then your code will be simpler as you will not have to care about the container of the input field. However, you will have to use this attribute carefully, as you may get a duplicate ID error if you use thisprepend attribute too often... link|improve this answer