Spring Boot报错"Export identifier encountered more than once"的原因与修复

Alright, let's unpack this "Export identifier encountered more than once" error you're facing, using the details about your three classes:

This is an ORM framework error (most commonly from Hibernate or JPA) that pops up when the framework can't generate or resolve a unique identifier for an entity. Put simply, it's confused because it's encountering duplicate "export identifiers"—the unique values (usually tied to your @Id annotated primary keys) that the framework uses to distinguish one entity instance from another.

Based on what you shared, here are the most likely culprits:

• TransactionComponent's missing accessors: You mentioned this class doesn't have getter/setter methods for its id. If TransactionComponent is a JPA @Entity, the framework needs to access its @Id field to manage unique identifiers—without getters/setters, it can't properly read or set the primary key, leading to confusion that spills over into related entities like OrderSignal or TransferSignal. Even if it's an @Embeddable class, missing accessors for its fields can cause the framework to misinterpret its properties as duplicate identifiers.
• Mapping conflicts between related classes: If OrderSignal or TransferSignal are linked to TransactionComponent (via @Embedded, @OneToOne, or another association), there might be a conflict in how their primary keys are mapped. For example, an embedded TransactionComponent might have fields that clash with the host entity's primary key setup, or the association configuration could lead the framework to think multiple entities share the same identifier.
• Hidden inheritance issues: Even though you said OrderSignal has no other @Id annotations, if it inherits from a parent class that does have an @Id, a misconfigured inheritance strategy (like missing @DiscriminatorColumn for single-table inheritance) could cause the framework to mix up identifiers across subclasses or related entities like TransferSignal.

Here are targeted steps to resolve the issue:

1. Fix TransactionComponent's accessor methods:
   • If it's an @Entity: Ensure it has an @Id annotated field, then add public getter and setter methods for that field. JPA relies on these methods to manage the entity's primary key—without them, identifier handling breaks down.
   • If it's an @Embeddable: Add getter and setter methods for all its fields. The framework needs to access these properties to properly embed the class into other entities, preventing misinterpretation as duplicate identifiers.
2. Audit mappings for OrderSignal and TransferSignal:
   • Check how these classes relate to TransactionComponent. If using @Embedded, make sure the embedded properties don't conflict with the host entity's primary key fields or mappings.
   • For associations like @OneToOne, verify that primary key generation strategies (e.g., @GeneratedValue) are unique across entities—avoid sharing the same sequence or generator that could produce duplicate IDs.
3. Validate inheritance configurations:
   • If your classes use inheritance, double-check the @Inheritance strategy. For example, if using single-table inheritance, ensure you have a @DiscriminatorColumn to distinguish between subclasses, so the framework doesn't confuse their identifiers.
4. Check entity scanning setup:
   • Make sure your JPA container (or Spring Boot) is scanning entity classes correctly—avoid duplicate scanning paths that would register the same entity multiple times, leading to identifier conflicts.

内容的提问来源于stack exchange，提问作者R.Schaefer