I could be way off here as I'm not very familiar with calling servlets from the action param but, shouldn't the action of the form be /tasking/TaskingServlet as that's what the url mapping has been set to.

You are calling your own servlet so why are you even bothering with h:commandButton? Just use a standard <input type=submit/> as you are bypassing JSF anyways aren't you?

To be honest with you I actually find it really odd that you need this behaviour in the first place. What is this servlet for? Why couldn't this just be a standard action that you call on a Seam bean?

There are many things about this scenario that don't make much sense to me but, I have no idea what you are doing so...I guess being confused is normal. :P

OK, after reading what you are doing I think that the servlet idea is the wrong way to approach the problem. If your entire GUI framework is using the Seam/AJAX/Richfaces stack then use it for this as well.

Your Seam bean should contain the list of TaskingDataObjects and this list should be used by a dataTable component or equivalent as it's value. Then you can put your inputs in this table.

Then you would put a commandButton on the form that would call an action method in this Seam bean that would do any extra processing you want on the items in this list.

A rough example here.

@Name("MySeamBean")
public class MySeamBean() {

    private List<TaskingDataObjects> tasks;

    //Call this method on the first visit to the page
    public void setup() {
        //Setup your tasks list here
        tasks = SomeMethodThatCollectsAllYourTaskingDataObjects();
    }

    public List<TaskingDataObjects> getTasks() {return tasks;}
    public void setTasks(List<TaskingDataObjects> list) {this.tasks = list;}

    public void doSomething() {
        for(TaskingDataObject task : tasks) {
            //Do whatever processing you require
        }
    }
}

in your xhtml

<h:form>
    <h:dataTable value="#{MySeamBean.tasks}" var="row">
        <h:column>
            <f:facet name="header">
                <h:output value="Attribute1"/>
            </f:facet>
            <h:inputText value="#{row.attribute1}"/>
        </h:column>
        <h:column>
            <f:facet name="header">
                <h:output value="Attribute2"/>
            </f:facet>
            <h:selectOneMenu value="#{row.attribute2}"/>
        </h:column>
        <!--And so on and so on for each attribute-->
    </h:dataTable>
    <h:commandButton value="DO SOMETHING" action="#{MySeamBean.doSomething()}"/>
</h:form>

I may not have completely understood your problem so if that's the case maybe you can explain why this solution wont work.

Cheers,
Tim

In answer to your question...Yes. :) Every instance in the list will be updated to whatever the users input.

Remember Seam with JSF is essentially binding what you see on the screen to the java objects in the back end.

So just like a simple inputText bound to SeamBean.username will be updated to the value the user typed in before they hit the login button the same applies to more complex types like lists or custom POJOs.

I would HIGHLY recommend reading the articles found in This Linke. It will really help you understand what's going on.

For all intents and purposes the Seam/JSF framework is really quite powerful and flexible. There are very few reasons that you would need to drop down to the servlet level. That being said I do have a couple of servlets on my app but they are mainly for content delivery of attachments and reports.