Skip to content

To understand the idGenerator field usage in MessageHeaders #36843

Description

@mjd507

The idGenerator static field in MessageHeaders looks always null, and no static setIdGenerator method provided.

but the static getGenerator method will check this null idGenerator first, then the default-idGenerator.

I see in spring integration, their IdGeneratorConfigurer will use reflection to set this idGenerator field.

I want to understand the design, its a little strange for me.

Originally posted by @mjd507 in spring-projects/spring-integration#11014 (comment)

Metadata

Metadata

Assignees

Labels

for: external-projectNeeds a fix in external projectin: messagingIssues in messaging modules (jms, messaging)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions