Skip to content

Conversation

@artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-3664

Since all metrics are already direct for the integration components, we don't do any proxying from IntegrationMBeanExporter,
and even any other adjustments during BPP phases. Hence this stuff is already redundant for IntegrationMBeanExporter.
In addition this change fix the early access to the BeanFactory from BPP issue.

JIRA: https://jira.spring.io/browse/INT-3664

Since all metrics are already direct for the integration components, we don't do any proxying from `IntegrationMBeanExporter`,
and even any other adjustments during BPP phases. Hence this stuff is already redundant for `IntegrationMBeanExporter`.
In addition this change fix the `early access to the BeanFactory from BPP` issue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs try...catch like super.

@garyrussell
Copy link
Contributor

Otherwise LGTM; I wonder if we should add a test to reload the same context in the same jvm to make sure all beans are unregistered (we probably should have had one with Lifecycle).

Also, we should add a bullet to the new JMX section in the reference to say that the IMBE no longer implements Lifecycle etc.

@artembilan
Copy link
Member Author

Pushed

@garyrussell
Copy link
Contributor

LGTM; doc polish here garyrussell@27b4ec3

I don't think we need to get into framework internals there (BPP etc).

@artembilan
Copy link
Member Author

Polishing accepted and pushed the fix according https://jira.spring.io/browse/SPR-12761 changes.
Need to wait for the SF master build before testing and merging

@garyrussell
Copy link
Contributor

Rebased; merged as 0f05512

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants