Last month, this column explored the high-level differences between the two competing Web service methodologies. The conclusion was that Sun Microsystems J2EE was best defined as a model or standard for building distributed applications, and Microsofts .NET was essentially a product suite for accomplishing the same goals. This month, youll see how each of these products could be used to build a real-world set of applications.
The hype surrounding J2EE and .NET has reached new heights of absurdity. I have read countless white papers and articles written by industry experts proving that J2EE is better than .NET, or one or the other is easier to use, less expensive to implement, more secure, or whatever. It seems to me that the ultimate goal of enterprise computing systems should be interoperability, not one-upmanship. If either J2EE or .NET becomes truly accepted, it will be because they workand work with other systems.
Back to the Real World
Recommended For You
Want to continue reading?
Become a Free PropertyCasualty360 Digital Reader
Your access to unlimited PropertyCasualty360 content isn’t changing.
Once you are an ALM digital member, you’ll receive:
- Breaking insurance news and analysis, on-site and via our newsletters and custom alerts
- Weekly Insurance Speak podcast featuring exclusive interviews with industry leaders
- Educational webcasts, white papers, and ebooks from industry thought leaders
- Critical converage of the employee benefits and financial advisory markets on our other ALM sites, BenefitsPRO and ThinkAdvisor
Already have an account? Sign In Now
© 2025 ALM Global, LLC, All Rights Reserved. Request academic re-use from www.copyright.com. All other uses, submit a request to [email protected]. For more information visit Asset & Logo Licensing.
