However, if my deployment is in UNIX environment, I doLook at it this way: .Net forces you to Microsoft platforms. No way out.
not even have to say anything to my boss. Certainly
JAVA is the only way to go.
The dilemma is really in how to explain why I selectIf they're equal, then the comparison is easy! ;-)
Java-based apps rather than .NET based apps. Have been
thinking for quite sometimes since then. It is
difficult to compare when the 2 objects are not equal.
idea of using both .NET(as front-end) and JAVA (as back-end) in all new project.This is an idea. From what I see, the .NET framework is being sold as an XML solution with XML, SOAP, and web services as key underlying technologies. What I don't see much of pertains to the implementations of these "web services". What .NET technologies are you thinking about using for the "front-end"? What Java technologies for the "back-end"? I guess you could develop the services using Web Services for J2EE. If all of your existing applications are using JSP for presentation, why change over to some .NET presentation technology. I'm not sure what this actually is, ASP pages?