|
From: <rod...@in...> - 2003-06-09 16:45:28
|
<juergen> One could say that Spring's relation to the iBATIS Database Layer is similar to its relation to WebWork or Struts: Spring offers similar functionality with differences in terms of modelling approach, but all of it integrated into one coherent approach for all application layers - while still being individually reusable. </juergen> Yes, I think the idea of consistent configuration via JavaBeans and total pluggability via interfaces is so powerful that a lot of things just fall into place because Spring provides powerful support for it. I completely agree regarding iBATIS DB layer. I wasn't quite sure what it set out to do. I would rather use Spring or Hibernate (Spring+Hibernate, that is) and be clear on whether I wanted a better JDBC or true O/R mapping. They're quite different things. <juergen> So it seems that we're on the right track: Some of the main design ideas that we've adopted keep emerging in bits and pieces of various other frameworks. Though in many cases for an isolated functionality domain, and often not drawn through as consequently. </juergen> Well put. I think a lot of people are thinking the same way: for example, I just read http://www.freeroller.net/page/ceperez today ("Proliferation of Java Microkernels and Extinction of J2EE Containers"). I think Spring has a unique value proposition in how it pulls everything into the one overall picture, while remaining lightweight (compared to things like JBoss AOP, which needs total control of the classloader, even in standalone form). It's vital that we sell that value proposition vigorously. When we release we must do our best to get traction in the community...just having a great technology isn't enough, without the marketing behind it. Btw, I think we definitely need a feature lockdown for 0.9. Necessary refactoring, bug fixing, yes, but no new areas to conquer. Spring is big enough for the near future; we need to tidy up and start selling it. Regards, Rod |