q张囄意思大致也是_目前的图书中Q关于Java, Java EE的书直就是多如牛毛，而关于Ruby和RoR的书只有2本（我现在在看的Q算是第3本吧QO'Reilly也有一本关于RoR的书Q算是第4本）?但是RoRq个新应用框架却正在以狂风暴雨之势席?Web 开发社区，特别是Java和PHP?/p>
汇M下网上的以及自己从书中看到的资料:
- 什么是Ruby?
Matsumoto Yukihiro Q?Matz"Q是Rubyq个~程语言的发明hQ他?993qv便开始着手Ruby的研发工作，1993q??4日Ruby诞生Q?995q?2月Matz推出了Ruby的第一个版本Ruby 0.95。Ruby 是一U动态编E语aQ它在许多方面类g Perl、Python ?SmalltalkQ但是它是自成体pȝQRuby成功的组合了Smalltalk的优雅以及Python的易用性，q有Perl的实用主义。Java ?PHP ~程人员应该可以很轻杄掌握q一语言?/p>
Ruby 的历史不短，先于?995 q便为公众知晓的 Java ?PHP。所以尽?Ruby 是一个成熟的语言Q却不如其它语言普及。这造成?Ruby ~程语言阵营q不?Java、PHP ?Perl 阵营强大Q这也是上面q张囑ֱC出来的现状Q?/p>
- 什么是Rails?
Rails是一个用来开发以数据库ؓ后台的Web应用的开源框架?David Heinemeier Hanson 发明?Rails 框架?Ruby 诞生以来最受欢q的应用E序QRuby C推广能力不济的颓势也得到了扭转。Rails ?Ruby ~程语言扩展为极光用?Web 开发的领域特定语言。它q借用?ActiveRecord 扩展Q将对象关系持久性引入了 Ruby 语言?/p>
Rails使用了严格的 Model-View-Controller (模式-视图-控制?体系l构Q赢得了自尊且醉心于设计模式的JavaE序员的敬 - q是 J2EE 开发h员对其情有独钟的原因Q?同时 Rails 可以非常方便地构建基pȝ - q是它吸?PHP 开发h员的原因?/p>
但Rails有它自己的一些薄q地方: 从数据库角度来看QRails 有一些非常明昄~陷。Rails Ҏ据库布局和应用程序需求作了许多假定。比如，Rails 假定所有表都用一个非复合的主键。它不支持复合主键也不支持双步提交（two-phase commitQ，它只能用于单个数据库后端的情c?/p>
- RoR的优?
Ruby on Rails最大的优点是在于单！RoR的核心思想是"更少的编E，更简单的配置Q?
- 安装和配|非常简单，不象Java需要安装运行环境，安装应用服务器，然后再进行一大堆的配|。Ruby只需要装一个简单的解释环境可以了。RoR避免了繁杂的XML配置文gQ你的应用程序和数据库里已经包含了所有Rails需要的东西?/li>
- ~码单，很多代码都是可以自动生成Q可以自动生成MVCQ可以自动生成框架、Web服务。甚至你只要写上一行代码就可以实现以前使用Java上百行代码的工作量，少的编E量意味着少的bug?/li>
- RoRE_吗，适合企业应用?
企业应用需要的是稳定和高效?Ruby和PHP一P属于解释性语a?目前使用PHP来开发的Web应用Q适合于企业应用的不少Qblogpȝ和讨论组pȝ也都大量使用PHP?配合Ruby的RoR在效率上应该没有什么问题?至于E_性，目前q没有什么实际的数据可以来讨论?/p>
【相关链接?/p>
Ruby: http://www.ruby-lang.org/en/
Rails: http://www.rubyonrails.org/
]]>
Groovy is a dynamic language for the JVM that integrates seamlessly with the Java platform. It offers a Java-like syntax, with language features inspired by Smalltalk, Python or Ruby, and lets your reuse all your Java libraries and protect the investment you made in Java skills, tools or application servers.
很早以前曾l关注过GroovyQ还在Ruby和Groovy中犹豫过?目前虽然在看一些Ruby和RoR的书c和资料QGroovyq是不会忽略掉的Q当然还?a target="_blank" class="externalLink" title="Grails">GrailsQ这个以Groovy写成的Web应用框架 (Groovy + Grails & Ruby + Rails)?/p>
【相关链接?/p>
下蝲Groovy: http://dist.codehaus.org/groovy/distributions
About Groovy: http://www.aboutgroovy.com/item/list
]]>
]]>
]]>
]]>
]]>
]]>
Eclipse需要保持竞争力Q关键也在于开发和使用者的q个C֛?Eclipse的plug-in架构Q已l保证了q个C会很快的成长Q因Z有大量的开发者去写plug-inQ，大公司（如IBMQBEAQBorlandQ的加入和支持，也扩大了Eclipse的知名度Q得更多的开发者加入进厅R?但是如何更好的融合这个社，如何保证Eclipse的核心基架构不受外部的困惑（变得更加庞大Q或者臃肿）但又会不断创斎ͼ如何协调好Eclipse和其他Eclipse.org下面的顶U项目（如BIRTQWTPQAspectJ{）的整合关p，q些Q确实也值得思考?
对interface~程Q这个似乎是个老生常谈的问题了Q但是却从来没有思考过Q这U编E方式会影响到这个开发团队的协同工作Q特别是一个超q?0人的开发团队，而对一个分布在不同地方的开发团队（比如目外包以后Q不同的开发小l位于不同的城市Q甚臛_ӞQ这U编E方式带来的影响更大?
Z么会q样呢？ 在一个只?-4人的开发团队里面，M的改动，可以快速的通知其他的hQ而且Q现在IDE中的重构工具会解军_部分的工作?但是Q当一个开发团队变大的时候，通常׃分成组Q不同的组对不同的部分负责?在这U情况下Q你在自q模块中发布了APIQ你必ȝ保这个API是稳定的。“Once you have published an API then it is your responsibility to keep them stable. Otherwise you will break the other components and nobody is able to make progress. Having stable APIs is a key to making progress in a project of this size.?所以这是一个是否把API发布以及发布了以后如何维护的问题Q“So it's the difference, as Martin Fowler would say, between public and published. Something can be public, but that doesn't mean you have published it. ?即定义了APIQ公开发布(publish)和这个API是公q(public)是有区别的：API公开发布以后Q就需要非常的心Q因ZQ何的API改动都可能会破坏其他在用这个API的代码?
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
EclipseQ?A rel=tag align="top">Design Pattern 
Programming
]]>
陆l更C些心得?
SoftwareQ?A rel=tag align="top">Design Pattern Programming
]]>
I just noticed that String#substring(? shares the underlying char array. So if you have a big string, take a substring of it, throw away the big string, you will still hold on the big char array. A simple way to solve this is to make a copy of the substring using the String(String) constructor.
I saved 550KB in JDT Core by changing the following code:
String simpleName =
fullyQualifiedName.substring(fullQualifiedName.lastIndexOf('.'));to
String simpleName = new
String(fullyQualifiedName.substring(fullQualifiedName.lastIndexOf('.')));
Eclipse3.1发布以后Q用者发玎ͼ3.1占据了大量的HeapQ大U?00-300MQ?/U>。Eclipse的开发小l正在不断地解决q个问题Q而String#substing的改q，在Eclipse 3.1M6中发?4???
q个提示Q其实也可以q用在我们自q目之中
[Note: This blog was migrated from my old CSDN blog.]
Z么重发这个blog呢？因ؓ昨天看到Eclipse.org|站上关?A >Eclipse Performance的一个文档。这份文档主要是提示Q在开发基于Eclipse的应用时Q不是EclipseE序本nQ还是Plug-inQ，在性能问题上需要注意的一些地斏V其中，W一条就是如何用substring()的问题。Eclipse 3.1M7以及RC1Q都已经q行了这斚w的调_所以现在的EclipseQ对Heap的占用已l大q减，从而在性能上也有所提高?
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
EclipseQ?A rel=tag align="top">Java EclipseQ?A href="http://www.tkk7.com/kukoo/category/1245.html">Programming
]]>
Software ProgrammingQ?A rel=tag align="top">Ruby Programming
]]>
..... The business layer should be responsible for the following:
- Handling application business logic and business validation
- Managing transactions
- Allowing interfaces for interaction with other layers
- Managing dependencies between business level objects
- Adding flexibility between the presentation and the persistence layer so they do not directly communicate with each other
- Exposing a context to the business layer from the presentation layer to obtain business services
Managing implementations from the business logic to the persistence layer
Excerpt from "Wiring Your Web Application with Open Source Java" by Mark Eagle
[NoteQ?/SPAN>This blog was migrated from my very old blog which was in the blogspirit.]
Software ProgrammingQ?A rel=tag align="top">Open Source Programming
]]>
- Managing requests and responses for a user.
- Providing a controller to delegate calls to business logic and other upstream processes.
- Handling exceptions from other tiers that throw exceptions to a Struts Action.
- Assembling a model that can be presented in a view.
- Performing UI validation.
Here are some items that are often coded using Struts but should not be associated with the presentation layer:
- Direct communication with the database, such as JDBC calls.
- Business logic and validation related to your application.
- Transaction management.
- Introducing this type of code in the presentation layer leads to type coupling and cumbersome maintenance.
Excerpt from "Wiring Your Web Application with Open Source Java" by Mark Eagle
[NoteQ?/SPAN>This blog was migrated from my very old blog which was in the blogspirit.]
Software ProgrammingQ?A rel=tag align="top">Open Source Programming
]]>
- Querying relational information into objects. Hibernate does this through an OO query language called HQL, or by using an expressive criteria API. HQL is very similar to SQL except you use objects instead of tables and fields instead of columns. There are some new specific HQL language elements to learn; however, they are easy to understand and well documented. HQL is a natural language to use for querying objects that require a small learning curve.
- Saving, updating, and deleting information stored in a database.
- Advanced object-to-relational mapping frameworks like Hibernate have support for most major SQL databases, and they support parent/child relationships, transactions, inheritance, and polymorphism.
Here are some items that should be avoided in the persistence layer:
- Business logic should be in a higher layer of your application. Only data access operations should be permitted.
- You should not have persistence logic coupled with your presentation logic. Avoid logic in presentation components such as JSPs or servlet-based classes that communicate with data access directly.
By isolating persistence logic into its own layer, the application becomes flexible to change without affecting code in other layers. For example, Hibernate could be replaced with another persistence framework or API without modification to the code in any other layer.
Excerpt from "Wiring Your Web Application with Open Source Java" by Mark Eagle
[NoteQ?/SPAN>This blog was migrated from my very old blog which was in the blogspirit.]
Software Programming, Open Source Programming
]]>
Bruce原来的blog: On the Thought是我常看的一个blog之一Q原因不仅仅是因为Bruce是Think in Java的作者，他也在blog中发表了相当有意思的帖子?
而Aitima的blogpȝ也挺有意思的Q你发表评论的时候，像是在一个论坛里面（那种很像BBS的论坛）。我没有扑ֈ如何trackeback Bruce的weblogQ但是这U发表评论的作法Q确实新颖。按照Bruce的介l，在发表评论的时候，也不是Q何东襉K可以发表的（要不变成了“blog spam”）Q因为Aritima Blog建立了一U机Ӟ“keep the discussions civilized ”，而且Artima更注重开发者。这两点Q是Bruceq移他的blog的原因?
如果你也xBruce EckelQ去他新?A >Webblog吧?
Bruce Eckel的homepage
Bruce Eckel的Weblog Feed
blogQ?/FONT>Software Programming Blog/RSSQ?/FONT>Programming
]]>
我第一接触StrutsQ大U在2001q的q中。那时候，我刚好结束了一个项目（我的W一个J2EE目Q，基本上是以Sun的PetStore的设计思想开发的Q其实，PetStore已经含有MVC 2的思想了）。我的一个朋友推荐我看看Struts。我一下子pStruts单，灉|而又高效的设计思\吸引了，特别是看到ActionForm可以“自动的”得到页面的输入Q而不需要自己写大量的request.getAttribute()的时候，几乎喜出望外了。当Ӟq没有够多的Struts的资料，市面上可以买到的Q也只有O'Reilley出版的唯一的一本关于Struts的书c。但是我q是毫不犹U地在W二个项目中使用了Struts。到如今Q我参与的所有的目Q都是基于Struts的?
5岁的p孩儿Q会赎ͼ会说话，刚刚q幼儿园。?岁的StrutsQ现在是Java世界里，开发Web应用E序的默认框架标准。在书店里，你可以找到大量的关于Struts的书QStruts的资料也是浩如烟说它“如日中天”可能也不ؓq?
然而，Struts也有它不的地方Q比如重用ActionForm和Action比较ȝQ，而同时新的技术又在不断涌玎ͼ5q_或者说3q_以后Q会是什么样子呢Q下一代的Web应用框架Q会是JSF?QJSF的作者就是Craig R. McClanahanQ或者，真的如Craig说的QJSF应该和Struts协同工作Q而不是替换掉Struts?
看看TheServerside上面大家的评?/U>吧?
Struts on Apache
Comments on TheServerside
5 Year Anniversary of the Birth of Struts
Sean's stack trace on Struts 5 Years .
JavaQ?/FONT>Software Programming EclipseQ?Programming
]]>
重用的最高境界是什么？我们创徏一个非帔R层的Q面向具体应用的框架Q然后只要做单的客户化，q且重用q个框架中现有的设计。（“We thought the way to create software was to build high-level, domain-specific frameworks, and then you just customize them and reuse all the design that is codified into them. That was the reuse nirvana.”）但是Q连Eric都意识到Q这太理惛_了，因ؓ ?I have learned that it's hard to create highly reusable frameworks.?
在谈到可重用的framework的时候，Eric提到?A href="http://www.tkk7.com/kukoo/admin/www.eclipse.org">Eclipse:
那么Q什么又是Controlled extensibility呢？Z么要Ҏ展性进行控制呢Q?
Eric对于重用Q定义了三个U别Q最低一U，重用c（classesQ；最高一U，框架QframeworkQ；而中间一U，是设计模式QDesign PatternQ（“This is where I see patterns. Design patterns are both smaller and more abstract than frameworks. They're really a description about how a couple of classes can relate to each other and interact with each other. The level of reuse increases when you move from classes to patterns and finally frameworks. ?
Eric提到了一个有的现象。通常Q我们拿C个需求，会先做设计，做设计的时候，我们会用设计模式（Design PatternQ。但是，使用XP QeXtreme ProgrammingQ方式的Zq样做，他们先写试Q“They write a test”）
那么Q设计一个framework的时候，要注意什么呢Q要避免frameworkitis. Q?Frameworks abstract and provide higher level default functionality. To do so the framework needs to be in control. This loss of control can lead to what is sometimes called frameworkitis. ”）
而且Q一个framework要做的比较小Q因为，如果framework太大了，那么它可能就会做太多Q可能会frameworkitisQ，而且Q不Ҏ学习Q学习曲U太长，也不Ҏl护?
Eria的论q真是非常精彩，而且也解释了Eclipse的一些内部设计。一定要阅读全文
[Update] 感谢lxwde的中文翻译。我的中文翻译可能不完全准确。中文翻译，请参考Related Links中给出的lxwde的中文翻译链接?BR>
Artima developer
访谈的第一部分
如何思考Design Pattern?
CSDN上的中文译
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
SoftwareQ?/FONT>Design PatternQ?/FONT>Eclipse Programming, Eclipse
]]>
“The complainer may talk about how this means that you can't tell if a particular team is using an agile method or not. They may also say that this makes it hard to teach people how to do agile methods - what's the curriculum?”（q些抱怨者指Z们很隑分是否在使用敏捷ҎQ也很难用固定的评L授如何用敏h法）
然而，没有一个严格的定义Q正是敏h法的核心哲学 Q“This lack of rigorousness is part of the defining nature of agile methods, part of its core philosophy.”）
Martin接着指出Q?
“Different kinds of systems have different kinds of pressures and forces, which makes it very difficult to come up with a rigorous statement of what to do that's sufficient to cover them.”（不同的系l有来自不同斚w的压力，q种情况使得很难定义Z个严格的q程Q去定义如何有效的解册些问题）
而另一关键的问题是QhQY件开发的MQ是一个最大的可变的因?Q“This effect is compounded by the fact that software development is such a people-oriented activity, and people are naturally inconsistent and highly variable. ”）
倡导敏捷Ҏ的hQ之所以没有ؓ敏捷Ҏ制定Z个严格的定义Q就是ؓ了将软g开发中最大的可变因素Q而又是过E的执行者：人，忽略掉。（?that's its not effective to try and bind software development to a rigorous process, because that's ignoring the essential nature of the primary (human) components that will execute that process”）
Martin Fowler
inconsistent and highly variable
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
SoftwareQ?A rel=tag align="top">Agile Programming Programming
]]>
作者提C几个有趣的事实。首先，Z览器的Web Application让IT部门的员工爱不释手，因ؓ真正的“零客户端管理”实CQ服务器端的M一Ҏ动在客户端立d可以使用了，而不需要每个客L都再ȝ护了。但是，除了q个好处之外Q还有其他什么吗Q用P包括IT部门的员工逐渐意识到了，有了易于理的好处，但是牺牲了可用性，许多非常好用的功能，比如鼠标右键的快捯单，按列重新排序Q调节列的宽度等{，都在Web Application中失M。而事实上Q仔l想惻IZ么大多数的用h愿意使用OutlookQThunderBirdq样的邮件客LQ而不是mail.yahoo.comq样的浏览器邮g客户端。而同Ӟ览器下的Web Application没有一个统一的应用程序的风格Q菜单放哪里Q上面，底下Q左下角Q?
再回来看看所谓的“零理”。J2SE 1.4中加ZJava WebStart的功能。这U分布式的做法，使得客户端每ơ启动执行的时候，都会从服务器下蝲最新的版本。这P不是解决了“零理”的问题了吗Q其实还有一些需要注意的问题Q下载多？如果每次都要下蝲好几兆的更新Q通常用户的接受不了。想xơ更新Windows的补丁，q道下载好几兆的更新是一U什么感受了?
所以，真正的网l客LQ应该是“瘦”的Q但是“功能丰富的”，或者说Q是“thin”而且“rich”。“thin”是指相对于传统的“fat”客LQ象Officeq样的“胖客户端”）Q在客户端不需要太多的安装Q“rich”则是指相对于当前的Web ApplicationQ应该是功能丰富的。当前的Web Application是“thin”的Q但是不够“rich”?
那么何去何从呢？
一个选择是Mozilla 的XULQ一个跨q_的UI解决ҎQ?BR>一个选择是Eclipse的RCPQ够的“rich”了Q但是不够“thin? RCP的运行库pC6.7M了，g胖了炏V?
看完q个blogQ只有两个想法：
其一QRCP应该会是一个很大的发展方向。需要下载安装的客户端对于高速的宽带|络来说Q不是问题；
其二QJava WebStart的应用，每次客户端启动，只会更新改动q的部分Q除非客h除了客户端的~存Q。这L话，6.7M的RCPq行库ƈ不是每次都需要更新的?
有了Java WebStartQWeb Application所U道的“零客户端管理”就不再是一个显著的优势了。而RCP却带来了Web Application所不具备的用户易用性，l一的风格和传统桌面E序中所熟悉的功能?
Wolfgang Paulus ?SwixML Q一个开源的XUL引擎Q的创始者和主要作者。也许Wolfgang更乐于看到XUL ?RCP 都会健康的发展，提供开发真正的“Thin Rich Web Application”的q_?
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
EclipseQ?A rel=tag align="top">RCP EclipseQ?A href="http://www.tkk7.com/kukoo/category/1245.html">Programming
]]>
SmallTalk快要完成它的历史命了Q而Q何一U语aQ不是Javaq是C#Q都不可能永q存zMȝ。技术主g了市场，新的需求会催生新的语言?
Email this story to a friend (send a short email with a subject to this story)
Richard Monson-Haefel?/FONT>BlogQ?/FONT>IBM abandons Smalltalk
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
]]>
Bobby Woolf 在他的blog中提Z使用Data ObfuscatorQ淆数据）Q即通过一个特定的E序Q特定的一l算法和规则Q从用户的数据中摘取_的数据量Q同Ӟ把一些敏感的数据Q如姓名Q薪_保险L{）替换成一些不重要Q或者不敏感Q的数据Q比如，把姓名用A001, A002来替换掉Q?
Bill Venners把q次访谈的内容分多次Q发表在Artima Developer上。Erich Gamma的论q确实精彩，他不仅谈C当初如何q入Design Patternq个领域的过E，也谈C在他开发JUnit的过E中Q如何设计JUnitQ以及如何在JUnit中用Design Pattern?
“Do not start immediately throwing patterns into a design, but use them as you go and understand more of the problem. Because of this I really like to use patterns after the fact, refactoring to patterns. ?. Trying to use all the patterns is a bad thing, because you will end up with synthetic designs—speculative designs that have flexibility that no one needs. These days software is too complex. We can't afford to speculate what else it should do. We need to really focus on what it needs. ?nbsp;“We didn't just string patterns together when we designed JUnit. We did it test-driven, starting with a test that we wanted to succeed and once it passed we looked into how we could improve the code. ?/SPAN>Who is Erich Gamma?Q这个问题好像问的有些傻Q?BR>《Design Patterns: Elements of Reusable Object-Oriented Software》，《Contributing to Eclipse: Principles, Patterns, and Plug-Ins》的作者之一QJUnit的作者之一QEclipse JDT的负责h。他目前在IBM的瑞士苏黎世OTI实验室工作?nbsp;
[Update]感谢?A >lxwde中文译?BR>
W一ơ访谈的详细内容?/FONT>
Artima Developer
CSDN 上的中文译
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
]]>
特别是Geronimo! Part1Q详l描qCGeronimo的系l结构。而Geronimo的开发，相比之前Q似乎加快了不少Q第二篇文章中就介绍了IBM开发的用于Geronimo的一个Eclipse构gQ但是需要和Eclipse WTP一同工作。希望Eclipse WTP可以把这个plug-in包含到WTP里面?
EclipseQ?A rel=tag>Geronimo
]]>
]]>