JSF+PrimeFaces多页面表单创建及数据存储异常问题求助

Hey Steven, let's tackle this multi-page form data persistence issue you're hitting with Java and PrimeFaces. This kind of back-and-forth where one page's data saves but the other doesn't almost always boils down to view state retention or data object initialization missteps—let's break this down step by step.

First: Fix Your Bean Scope #

If you're using @RequestScoped for your backing bean, that's a huge red flag. Request-scoped beans get recreated on every single page request, so any data entered on the first page gets wiped as soon as you navigate to the second.

Switch to @ViewScoped (for JSF 2.2+ or PrimeFaces' own @ViewScoped if you're using their extensions) instead. This scope keeps your bean alive as long as you're working within the same view context—perfect for multi-step forms. Example:

@ViewScoped
@ManagedBean
public class YourFormBean implements Serializable {
    // Your properties and methods here
}

Second: Stop Reinitializing Your Data Objects in the Save Method #

Looking at your code snippet, you're doing this:

PRPKUserNonIt PRPKUser = new PRPKUserNonIt(); 
PRPKUser prpkUser = new PRPKUser();

If you're creating new instances of your data objects inside the save method, you're overwriting all the data that was bound from the first and second pages! Instead, initialize these objects once when the bean is created, using @PostConstruct:

private PRPKUser prpkUser;
private PRPKUserNonIt prpkUserNonIt;

@PostConstruct
public void init() {
    prpkUser = new PRPKUser();
    prpkUserNonIt = new PRPKUserNonIt();
}

Now, when users enter data on page 1 and 2, it's all stored in the same instance of prpkUser/prpkUserNonIt that you'll save to the database.

Third: Ensure Proper Navigation & Form Submission #

When moving from page 1 to page 2, don't use a plain redirect (?faces-redirect=true)—that breaks the view scope and resets your bean. Instead, return the page name directly from your navigation method:

public String goToSecondPage() {
    // Optional: Add validation for page 1 fields here
    return "secondPage"; // No redirect, keeps view state intact
}

Also, make sure your page navigation buttons are submitting the form. For example, on page 1:

<h:form>
    <!-- Page 1 inputs bound to your bean's properties -->
    <p:inputText value="#{yourFormBean.prpkUser.firstName}" required="true" />
    
    <!-- Submit form and navigate -->
    <p:commandButton value="Proceed to Page 2" action="#{yourFormBean.goToSecondPage}" ajax="false" />
</h:form>

Fourth: Debug to Confirm Data Flow #

Add simple logging in your save method to check which fields are null before persisting:

public String save(){
    String nextPage = "";
    
    // Log all fields to see what's missing
    System.out.println("First name from page 1: " + prpkUser.getFirstName());
    System.out.println("Email from page 2: " + prpkUser.getEmail());
    
    try {
        // Persist the pre-initialized objects (not new ones!)
        yourDatabaseDao.save(prpkUser);
        yourDatabaseDao.save(prpkUserNonIt);
        nextPage = "success?faces-redirect=true"; // Safe to redirect after save
    } catch (Exception e) {
        e.printStackTrace();
        nextPage = "error";
    }
    return nextPage;
}

This will tell you exactly whether the issue is that data never made it to the bean, or if it's being lost during save.

Quick Recap of the Most Likely Fixes #

1. Swap @RequestScoped for @ViewScoped to retain data across page transitions.
2. Remove the new object instantiations in your save() method—use the ones initialized in @PostConstruct.
3. Avoid redirects between form pages to keep the view state alive.

Give these changes a shot, and let me know if you still run into issues!

内容的提问来源于stack exchange，提问作者Steven a