Finally, see for yourself. Sun, Microsoft, and other vendors have conveniently provided a set of resources that simplify the processes of exploring and comparing .NET and J2EE, and highlight both the common elements and the ways in which the approaches diverge.
Sun created a Java Pet Store reference application as part of its Java blueprint. This sample application is representative of common enterprise applications. For example, it includes components for customer, order, product, and shopping cart implementations. It's a nontrivial reference, with more than 700 individual files in the 1.3 version. Not surprisingly, Microsoft and other vendors have seized upon the Pet Store application to showcase their products. Microsoft's version provides a useful means of comparing the .NET and J2EE approaches, especially in terms of understanding the different component middleware approaches embodied in EJB and .NET components.
Don't Worry, Make Users Happy
If you're like most enterprises, you'll migrate gradually to J2EE and .NET. Especially during tight economic times, nobody is eager to "rip and replace" working applications, and most enterprises will wait for more case studies before placing strategic bets on either technology.
Enterprises that focus on common areas between J2EE and .NET will benefit most because they'll leverage the transferability of skills and produce more reusable application components by using analysis and design techniques that apply to both, such as OO analysis and design using UML. Clearly, enterprises should work with their application and service suppliers to ensure that the suppliers' J2EE/.NET priorities align with their own. It would be unfortunate, for example, if a .NET-committed shop learned that its leading application vendor was leaning toward J2 EE instead of .NET—although it wouldn't exactly be the end of the world, thanks to XML Web services interoperability.
Almost all organizations will use a mix of J2EE and .NET, in part because the underlying platform choices are often dictated by existing application decisions. If your accounting department is already running Microsoft Great Plains, a J2EE version isn't likely to appear soon. Also, most organizations already use a mix of legacy Microsoft and Java-based tools and services, with the possible exceptions of Microsoft itself and some of the J2EE vendors, such as Sun.
Overall, you should anticipate that the coming enterprise architecture model will result in a raised least common denominator for enterprise applications and middleware, which will simplify and extend what was previously possible. Perhaps most significantly, as back-end development tasks are simplified, you'll actually be able to devote more attention to areas that directly impact the user experience and productivity. Imagine the benefits that directly impact user experience and productivity, such as a richer user experience and support for multiple device types. PDAs, smart phones, set-top boxes, and game consoles could be your next calling
更多軟考資料請訪問：考試吧軟件水平考試欄目
希望與更多網友交流，請進入考試吧軟件水平考試論壇
