MyEclipse 下开发JSF教程
随机数的困惑(java.util.Random/Math.Random()
WorkbenchAdvisor中的方法执行顺序
Struts 的安装、配置与运行
JDK1.5 最新特性
配置 Tomcat 的网站根目录、虚拟目录、端口等
彻底解决Tomcat 5.0.19中文乱码
深入探索SOAP1.1--使用SAAJ1.2.1
jfreechart里在页面上生成临时图片的过程剖析
今天一位老兄回的贴，觉得不错．
页面导航：
正文内容：60% jdbc
20% homegrown persistence framework
10% o/r mapping tools
5% java data objects (jdo)
5% ejb cmp / bmp
0% service data objects (sdo)
considering that orm only has 10% of the market, and "seldom is a good choice in systems typically with very large dataset and complex queries" one can wonder what the fuss is all about?
why not settle for a common abstraction layer and let each run according to own taste. it should be obvious by now that it is never going to be any consensus between the different persistence camps.
one big advantage is that it will not be necessary to frisk for weapons at the entrance to conferences and seminars! :)
yi zhou:
"i propose a cohesive persistence layer based on spring persistence layer"the obvious solution. (think logic, reason, common sense. exist for both java and .net) can anyone imagine how much money that could be saved by this approach? all over the world?
unfortunatly there is never possible to settle for anything obvious as long as a committee is involved.
regards
rolf tollerud
