Announcement Announcement Module
No announcement yet.
ClassPathBeanDefinitionScanner use Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • ClassPathBeanDefinitionScanner use

    How do I enable a ClassPathBeanDefinitionScanner in my spring.xml config such that it would execute after the other beans in the app context have been defined/created?

    My goal is to use the Scanner to auto-generate remoting proxies on the client tier and remoting exporters/invocation listeners on the server tier.

    Of course I could execute it as part of the logic in a BeanFactoryPostProcessor, but I don't really like that idea. It would be far nicer if I could specify it on the <context:component-scan/> element directly.

    Anyone know if this can be done or if I'm just stuck using a BeanFactoryPostProcessor?

    I've already opened a Jira Issue to support a slightly different use case, which is what I _really_ want, but I'm looking for any suggestions to tie me over until that can be resolved.