Spring MVC中能否通过视图href传递完整对象并在控制器接收？

Great question! Let's cut to the chase: you can't pass a full Java object directly via an href link in Spring MVC—since HTTP links only handle string-based parameters. But don't worry, there are reliable workarounds to get your object into the controller. Here are the most common approaches, with code examples:

1. Serialize the Object to JSON (and Deserialize in Controller) #

You can convert your object to a JSON string, pass it as a request parameter, then parse it back into an object in the controller. This works for small to medium-sized objects.

View Example (using Thymeleaf): #

<!-- Assuming `myObject` is in your model -->
<a th:href="@{/receive-object(objectJson=${#json.toJson(myObject)})}">Send Object via JSON</a>

Controller Example: #

import com.fasterxml.jackson.databind.ObjectMapper;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestParam;

@GetMapping("/receive-object")
public String receiveObject(@RequestParam String objectJson, Model model) throws IOException {
    // Deserialize JSON back to your object
    ObjectMapper objectMapper = new ObjectMapper();
    MyCustomObject myObject = objectMapper.readValue(objectJson, MyCustomObject.class);
    
    // Use the object as needed
    model.addAttribute("receivedObject", myObject);
    return "object-details";
}

⚠️ Caveats:

• GET request URLs have length limits (varies by browser/server), so this isn't ideal for large objects.
• JSON will be visible in the URL, so don't use this for sensitive data.

2. Pass the Object's Unique ID (Load from Database/Cache) #

This is the most recommended approach—it's secure, efficient, and avoids serialization headaches. Instead of passing the entire object, send its unique identifier (like an ID), then fetch the full object from your database or cache in the controller.

View Example: #

<a th:href="@{/load-object(id=${myObject.id})}">Load Object by ID</a>

Controller Example: #

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestParam;

@GetMapping("/load-object")
public String loadObject(@RequestParam Long id, Model model) {
    // Fetch the object from your repository
    MyCustomObject myObject = myObjectRepository.findById(id)
        .orElseThrow(() -> new IllegalArgumentException("Invalid object ID"));
    
    model.addAttribute("loadedObject", myObject);
    return "object-details";
}

✅ Benefits:

• Short, clean URLs.
• No data exposure in the URL.
• Works for any size of object.

3. Store Object in Session (Pass a Session Key) #

If you need to pass a large object temporarily, you can store it in the user's session, then pass a key via the href to retrieve it in the controller.

Step 1: Store Object in Session (e.g., in a previous controller): #

@GetMapping("/prepare-object")
public String prepareObject(HttpSession session, Model model) {
    MyCustomObject myObject = new MyCustomObject();
    // Populate object data...
    
    String sessionKey = "tempObject_" + System.currentTimeMillis();
    session.setAttribute(sessionKey, myObject);
    model.addAttribute("sessionKey", sessionKey);
    
    return "object-link-page";
}

Step 2: View Link: #

<a th:href="@{/get-from-session(key=${sessionKey})}">Get Object from Session</a>

Step 3: Retrieve from Controller: #

@GetMapping("/get-from-session")
public String getFromSession(@RequestParam String key, HttpSession session, Model model) {
    MyCustomObject myObject = (MyCustomObject) session.getAttribute(key);
    
    // Clean up the session to avoid clutter
    session.removeAttribute(key);
    
    if (myObject == null) {
        return "error";
    }
    
    model.addAttribute("receivedObject", myObject);
    return "object-details";
}

⚠️ Caveats:

• Session data is temporary and tied to the user's session (expires after timeout).
• Not ideal for shared links (since the key is tied to one user's session).

Key Notes & Best Practices #

• Avoid direct object passing: HTTP doesn't support it natively, so workarounds are required.
• Prefer the ID approach: It's the most robust and secure option for most use cases.
• Sensitive data? Use POST: href uses GET, which exposes data in the URL. For sensitive objects, use a form with method="POST" instead.

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