I'll try to outline what I would have done:

1) Create a bean that stores the fieldValue (the desired number of fields)

2) Create a form for the fieldValue that navigates to the page where the
dynamic form is displayed once it is submitted, e.g.
action="#{toDynaForm}". You need to specify a navigation rule in the
faces-config.xml for this.

3) The dynaform page should contains at least something like this:
    <h:form action="#{ActionClass.processForm}">
    <h:panelGrid binding="#{dynamicForm.formElements}" />
    </h:form>

4) Now have a look at the DynamicForm class I earlier posted. First, you
fetch the fieldValue from the bean that was sent. Then, you can create a
for-loop which just generates the desired HtmlInputText() objects.

5) Every HtmlInputText object needs to be binded to a bean variable.
(see the DynamicForm example). That's what the 'setValueBinding' method
does.

In your case, I think there's no clean solution to create a bean that
efficiently stores this values. I'd create a bean with a HashMap. When
the dynamicForm is built, you can initialize this map with keys that
have empty values. For example, each time a new HtmlInputText() is
created, you add a record to the map:
    Map().put(""+fieldValue+counter, "");  (Where counter increments for
every field within the current row).
Now, you can bind the field value to the value of this key:
    String bind = "#{Map[""+fieldValue+counter]}";
        hit.setValueBinding("value",
        getApplication().createValueBinding(bind));

6) When the dynaform page is submitted, you can fetch the bean Map in
the processForm() function and upload the data to a database.

I am no JSF expert, and it took me some time to understand this, too :)
I do think that this implementation conforms to the JSF framework the
most, but there might be easier (but dirtier) solutions using old JSP tags.