posted 18 years ago
Don't know if you can make a true "either or" case. If a company was already developing with Microsoft technologies then .Net might be the better choice for them. Setting EJB aside, the "Java" vs ".Net" discussion tends to come down to knowing what your target deployment environment is. If .Net doesn't exist on the kinds of servers you want to use, then you kinda know what you need to know.
I think the more feasible discussion is, if you are using Java, when do J2EE technologies like EJB make sense. EJB has complexity, but it also has power. Big applications with complex transactional, performance, and failover issues win by using EJB and other J2EE options. Smaller applications could win more by using something like Spring and ignoring the lion's share of the J2EE architecture. Just depends on what you are trying to do.
Reid - SCJP2 (April 2002)