ClassPathBeanDefinitionScanner - enhanced implementation

[lhazlewood]

I'm currently working on a ClassPathBeanDefinitionScanner implementation that allows one or more BeanDefinitions to be created and registered at startup based on a single annotation, on either a Class or an Interface.

The impetus for this issue is to support a cleaner and hands-off remoting scenarios:

When the application starts up, if the scanner finds an Interface annotated with the @Service annotation, the following will happen:

1. In the client tier, remoting proxy stubs will be auto-created.
2. In the server tier, remoting service Exporter objects will be auto-created.

This effectively allows one to annotate their service interface only, and have all the necessary remoting infrastructure set up. Naturally this could be applied for other mechanisms, not just for remoting.

Is anyone from SpringSource interested in collaborating on this? I could post to my blog, but I'd just assume put this in Spring's sandbox in revision control (as I've done before in the past). I just haven't done anything like this since SpringSource was formed, so I don't know the protocol of how to engage by adding this kind of support. I've already created an issue here: http://jira.springframework.org/browse/SPR-5583.

Let me know,

Cheers,

Les
http://www.leshazlewood.com