＋设为首页 ＋添加到收藏夹
this months ejb home was originally a presentation at jc2 in santa clara, california, in september. for those of you who couldnt make the session, i thought it would be beneficial to transcribe it here and relay an experience in the successful implementation of an ejb application using xp.
ejb/xp overview
i attended a boulder java users group in august. the topic was xp. the speaker asked, "how many of you know what xp is?" and half the attendees raised their hands. next, he asked, "how many of you have practiced xp on a project?" and half of the hands dropped. the next question he should have asked was, "from those of you remaining, how many have practiced xp on an ejb development effort?" quite frankly, i dont think many hands wouldve remained!xp is a methodology for software development that turns previous methodologies on their heads. it takes commonsense software development ideas, such as code reviews, unit testing, and integration testing, to the extreme while maintaining some general goals. these goals are risk management, producing high-quality software, building real applications (not massive frameworks), and, last but not least, having fun!
to accomplish these goals, xp advocates a number of "enablers," including simple designs, an iterative development process with pairs of programmers working side by side, and a heavy emphasis on unit testing (see figure 1).
enterprise javabeans is an integral api in the j2ee platform and the foundation of suns approach to server-side component models. ejb has been taking the software development industry by storm, especially in the e-commerce space, where n-tiered transaction-processing systems reign. ejb offers many features that enable your team to accomplish the goals of xp.
both ejb and xp are relatively new, and development organizations are often reluctant to take on too many paradigm shifts in their development process at one time. in general, this caution is warranted; however,... 下一页