Java数据库邮箱验证：新增账号前校验合法性及唯一性

Got it, let's work through adding email validation and duplicate checks before saving an account to your database. I'll break this down into actionable steps that fit your existing setup (Controller class, accManager view method triggering newAccount):

First, you need to ensure the email follows a valid format. You have two reliable options here—pick the one that fits your workflow best:

Option 1: Use Java's Built-in InternetAddress (Recommended) #

This method handles edge cases that regex can miss. Add this utility method to your Controller or a dedicated helper class:

private boolean isValidEmail(String email) {
    try {
        InternetAddress emailAddr = new InternetAddress(email);
        emailAddr.validate();
        return true;
    } catch (AddressException ex) {
        return false;
    }
}

Note: You’ll need to import javax.mail.internet.InternetAddress and javax.mail.internet.AddressException for this to work.

Option 2: Use a Robust Regex Pattern #

If you prefer regex, here’s a battle-tested pattern to validate email formats:

private boolean isValidEmail(String email) {
    String emailRegex = "^[a-zA-Z0-9_+&*-]+(?:\\.[a-zA-Z0-9_+&*-]+)*@(?:[a-zA-Z0-9-]+\\.)+[a-zA-Z]{2,7}$";
    Pattern pattern = Pattern.compile(emailRegex);
    return email != null && pattern.matcher(email).matches();
}

Next, you need to verify if the email is already registered in your database. This requires a DAO (Data Access Object) method to query existing entries.

Step 2.1: DAO Layer Query Method #

Add this method to your account DAO class (adjust the query based on your table structure and ORM):

public boolean doesEmailExist(String email) {
    String query = "SELECT COUNT(*) FROM accounts WHERE email = ?";
    
    // Example using JDBC (adjust for JPA/Hibernate if you use an ORM)
    try (Connection conn = getConnection();
         PreparedStatement stmt = conn.prepareStatement(query)) {
        stmt.setString(1, email);
        ResultSet rs = stmt.executeQuery();
        if (rs.next()) {
            return rs.getInt(1) > 0;
        }
    } catch (SQLException e) {
        e.printStackTrace(); // Replace with proper logging in production
    }
    return false;
}

Step 2.2: Inject the DAO into Your Controller #

Make sure your Controller can access the DAO (use constructor injection, @Autowired, or your framework’s preferred method):

private AccountDao accountDao;

// Constructor injection example
public YourController(AccountDao accountDao) {
    this.accountDao = accountDao;
}

Now update your Controller’s newAccount method to run both validation steps before saving the account. Here’s how that might look (assuming you’re using JSF for your XHTML view):

public String newAccount(String email, String username, String password) {
    // First, validate email format
    if (!isValidEmail(email)) {
        FacesContext.getCurrentInstance().addMessage(null, 
            new FacesMessage(FacesMessage.SEVERITY_ERROR, "Invalid Email", "Please enter a properly formatted email address"));
        return "createAccount.xhtml"; // Redirect back to the form
    }

    // Then, check for duplicate email in the database
    if (accountDao.doesEmailExist(email)) {
        FacesContext.getCurrentInstance().addMessage(null, 
            new FacesMessage(FacesMessage.SEVERITY_ERROR, "Email Already Registered", "This email is linked to an existing account"));
        return "createAccount.xhtml";
    }

    // If both checks pass, save the new account
    Account newAccount = new Account(email, username, password);
    accountDao.save(newAccount);

    // Add success message and redirect to login/home
    FacesContext.getCurrentInstance().addMessage(null, 
        new FacesMessage(FacesMessage.SEVERITY_INFO, "Account Created", "Your account has been successfully registered"));
    return "login.xhtml";
}

Add a message component to your XHTML form to display error or success messages to the user:

<h:messages globalOnly="true" styleClass="message-container" 
            infoStyle="color: green; font-weight: bold;" 
            errorStyle="color: red; font-weight: bold;" />

This will render the messages you added in the Controller when the form is submitted.

For high-traffic apps, there’s a tiny window where two requests could check for the same email simultaneously. To block this, add a unique constraint on the email column in your database:

ALTER TABLE accounts ADD CONSTRAINT unique_account_email UNIQUE (email);

Then update your DAO’s save method to catch the duplicate exception and handle it gracefully:

public void save(Account account) {
    try {
        // Execute save logic (JDBC/ORM code)
    } catch (SQLIntegrityConstraintViolationException e) {
        throw new DuplicateEmailException("This email is already registered");
    }
}

That’s all! These steps ensure you validate email format, check for duplicates, and give clear feedback to users before saving any account data.

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