We're trying to use the vanilla Spring <context:mbean-export .../> and the Spring Integration <int-jmx:mbean-export /> but run into problems. These two seem to have different requirements as to whether cglib is required for example.
We have a large number of @ManagedResource annotated Spring beans, and a fair few SI artifacts. It would be nice if the SI mbean exporter could just expose the SI components without interfering with the vanilla mbean exporter. If we just use the vanilla <context:mbean-export .../> then everything works fine, but if we include the <int-jmx:mbean-export /> then many (but not all) of the @ManagedResource annotated beans break.
Is there a way to use these two approaches together?