控制器未接收参数求助：传递JS生成的applicationNo失败

Hey there! Let's tackle this null pointer issue you're facing when passing the dynamically generated applicationNo parameter from your form to the controller. That red-highlighted value you mentioned isn't making it through properly—let's break down the most likely fixes step by step.

1. Make Sure Your Dynamically Generated Input is Properly Linked to the Form #

First off, double-check that the <input> element your JavaScript creates has the correct name attribute (this is what the controller uses to map the value) and is actually inside the <form> tag. Your JS should generate something like this:

<input type="hidden" name="applicationNo" value="THE_RED_HIGHLIGHTED_VALUE">

Here’s a solid example of how to create and attach it properly with JS:

// Create the hidden input field
const appNoInput = document.createElement('input');
appNoInput.type = 'hidden';
appNoInput.name = 'applicationNo'; // Critical: Match this to your controller's parameter name
appNoInput.value = 'INSERT_YOUR_GENERATED_VALUE_HERE'; // Replace with your actual red-highlighted value

// Attach it directly to your form
const targetForm = document.getElementById('grp...'); // Use your form's actual ID
targetForm.appendChild(appNoInput);

2. Ensure the Input Exists Before the Form Submits #

Sometimes timing is the issue—your JS might run too late, or the form might submit before the input is created. Fix this by hooking into the form’s submit event to guarantee the input is ready:

document.getElementById('grp...').addEventListener('submit', function(e) {
    // Check if the input already exists
    let appNoInput = this.querySelector('input[name="applicationNo"]');
    
    // If not, create and add it
    if (!appNoInput) {
        appNoInput = document.createElement('input');
        appNoInput.type = 'hidden';
        appNoInput.name = 'applicationNo';
        appNoInput.value = 'YOUR_GENERATED_VALUE';
        this.appendChild(appNoInput);
    }

    // Quick debug check to confirm the value is set
    console.log('Submitting applicationNo:', appNoInput.value);
});

3. Verify Controller Parameter Binding #

Make sure your controller is listening for the exact same parameter name as your input’s name attribute. For example, if you’re using Spring MVC:

@RequestMapping("/view_grp_conn_applications")
public String handleGroupApplicationRequest(@RequestParam("applicationNo") String applicationNo) {
    // Your business logic here
    return "your-view-name";
}

If you’re using a model class instead, ensure the class has a applicationNo field with proper getter and setter methods.

4. Debug the Request in Your Browser #

Use your browser’s dev tools to confirm the parameter is actually being sent:

1. Hit F12 to open Developer Tools
2. Go to the Network tab
3. Submit your form, then find the view_grp_conn_applications request
4. Check the Form Data section—you should see applicationNo listed with your red-highlighted value.

If it’s missing here, the problem is definitely on the frontend. If it’s present but your controller still throws a null pointer, double-check your backend parameter mapping.

5. Alternative: Pass the Parameter via the Action URL #

If form-based submission still gives you trouble, you can append the parameter directly to the form’s action URL:

const targetForm = document.getElementById('grp...');
const generatedAppNo = 'YOUR_RED_HIGHLIGHTED_VALUE';
targetForm.action = `${baseURL}view_grp_conn_applications?applicationNo=${generatedAppNo}`;

Your controller can still pick this up with @RequestParam just like before.

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