All you need to do is basically indeed just adding an empty object to the datamodel behind the value attribute of h:dataTable. But the same empty row needs to be preserved in the subsequent request as well. If the backing bean is request scoped, then the datamodel get reloaded without the empty row. This all … Read more
I got the answer on my own, it might seem weak, and too simple, but it works. Ready for this awesomeness..? Just add a timer of 0 to the focus…for some reason it just gives it enough time to fully load the input into the DOM. function recipientDivHandler(code, element) { $(“#recipientsDiv”).append(‘<input type=”text” id=”toInput” class=”inlineBlockElement rightSpacer” … Read more
I’d use a <h:dataTable> in a composite component with a backing UIComponent which you can bind by componentType attribute of the <composite:interface>. In the backing UIComponent you can then maintain the DataModel and define the actions. dynamicFieldList.xhtml <ui:composition xmlns:f=”http://java.sun.com/jsf/core” xmlns:h=”http://java.sun.com/jsf/html” xmlns:ui=”http://java.sun.com/jsf/facelets” xmlns:cc=”http://java.sun.com/jsf/composite” > <cc:interface componentType=”dynamicFieldList”> <cc:attribute name=”value” type=”java.util.List” required=”true” /> </cc:interface> <cc:implementation> <h:dataTable id=”table” binding=”#{cc.table}” … Read more
either (plain js) this.checked = false; or (jQuery) $(this).prop(‘checked’, false); // Note that the pre-jQuery 1.6 idiom was // $(this).attr(‘checked’, false); See jQuery prop() help page for an explanation on the difference between attr() and prop() and why prop() is now preferable. prop() was introduced with jQuery 1.6 in May 2011.
Use an iterating component like <h:dataTable> or <ui:repeat> to display a dynamically sized List of entities. Make the bean @ViewScoped to ensure that the list is remembered across postbacks on the same view instead of recreated over and over. Kickoff example with <h:dataTable> (when using <ui:repeat> simply replace <h:dataTable> by <ui:repeat>, and <h:column> by e.g. … Read more
Since the origin is actually not XML, but a Javabean, and the other answer doesn’t deserve to be edited into a totally different flavor (it may still be useful for future references by others), I’ll add another answer based on a Javabean-origin. I see basically three options when the origin is a Javabean. Make use … Read more