Aug 22nd, 2007, 09:36 AM
Wiring of non Spring container-managed bean tree with a multi-impl Bean
I have a conceptual problem with my application and so I hope you could help me.
I have a business layer that comes with its own domain objects. It is an EJB-base application.
These domain objects (pure POJOs) have to be used by differents UI Web applications in a low coupled manner.
I want to be able to change my business domain objects without impacting the "client" UI Web applications, just having to re-define my UI wrappers wiring.
My different client UI applications can be a N-version and a N+1-version of the same application, or a sticly different one.
I have considered using Spring to build the UI domains, and to dynamicaly wire these with the business objects. The new Spring 2.x <aop:scoped-proxy> element can help me to proxying my legacy business domain objects.
I don't know if it is a good way to achieve such a wiring and if there are some known limitations (performance, ...) or if there is a better way to do it.
If you have some ideas about it , please let me know ...