如何阻止JAXB在调用Getter方法时初始化列表？

Hey there! I get it—JAXB's default behavior of auto-initializing lists in getter methods can be annoying if you want more control over when collections are created. Let's walk through how to fix this so your generated getters just return the raw field without that null check and initialization code.

Option 1: Use a JAXB Binding File (For Code Generation from XSD) #

This is the standard way to customize JAXB's code generation behavior. Here's what you need to do:

1. Create a binding.xml file with the following content:

<jaxb:bindings xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" version="2.2">
    <jaxb:globalBindings>
        <!-- This flag disables auto-initialization of collections in getters -->
        <jaxb:initializeCollections>false</jaxb:initializeCollections>
    </jaxb:globalBindings>
</jaxb:bindings>

The key here is the <initializeCollections> element set to false—this tells JAXB not to add that null-check-and-initialize logic to your list getters.

2. Use the binding file with your code generation tool:
   • If you're using the xjc command line tool, pass the binding file with the -b flag:

     xjc -b binding.xml your-schema-file.xsd
     

   • If you're using Maven with the jaxb2-maven-plugin, add the binding file to your plugin configuration:

     <plugin>
         <groupId>org.codehaus.mojo</groupId>
         <artifactId>jaxb2-maven-plugin</artifactId>
         <version>2.5.0</version>
         <executions>
             <execution>
                 <goals>
                     <goal>xjc</goal>
                 </goals>
             </execution>
         </executions>
         <configuration>
             <bindingFiles>
                 <bindingFile>src/main/resources/binding.xml</bindingFile>
             </bindingFiles>
         </configuration>
     </plugin>
     

Once you run the generation, your getter will look exactly like you want:

public List<String> getMyList() {
    return this.myList;
}

Option 2: Manual Setup (For Handwritten Classes) #

If you're writing your JAXB classes by hand instead of generating them from an XSD, you can skip the auto-initialization entirely by:

• Using @XmlAccessorType(XmlAccessType.FIELD) to let JAXB access fields directly (optional but cleaner)
• Writing your getter to return the field without any initialization:

import java.util.List;
import javax.xml.bind.annotation.XmlAccessorType;
import javax.xml.bind.annotation.XmlAccessType;
import javax.xml.bind.annotation.XmlElement;

@XmlAccessorType(XmlAccessType.FIELD)
public class YourClass {
    @XmlElement(name = "myList")
    private List<String> myList;

    public List<String> getMyList() {
        return myList; // No null check, no auto-initialization
    }

    // Add setter if needed
    public void setMyList(List<String> myList) {
        this.myList = myList;
    }
}

Important Note #

Keep in mind that disabling auto-initialization means calling getMyList() could return null if the field hasn't been set yet. You'll need to handle potential NullPointerExceptions in your code—this is the trade-off for having more control over collection initialization.

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