This content has been marked as final. Show 9 replies
That's precisely the point. If the applications are to deployed in Windows environment, certainly .NET has more advantage as compared to JAVA. With any dev tools out there to support JAVA, it still difficult to outrun the available .NET dev tools.
However, if my deployment is in UNIX environment, I do 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 select 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.
I hope i could hear more from those who faced similar experience and managed to convince either the boss or team to proceed with Java.
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.
J2EE can run on any platform and product including Open Source, all
depending on your budget and needs.
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?
Has the Director provided any reasons or alleged benefits of making the change, or making "hints" of change? If you posted this information, it could be used to build a case.
J2EE it's a standard done by a lot of companies and used by a lot of people (and companies too). .NET it's not a standard.
In other words, j2ee it's oracle, hp, sun, ibm, etc........... and .NET it's only Microsoft.
This is transated, between other things, into a lot of differents implementations of same standard (all compatibles).
Implementations of java virtual machine (core of java):
Sun implementation: http://java.sun.com/j2se/1.4.2/download.html
blackdown implementation: http://www.blackdown.org/java-linux/java-linux-d1.html
IBM Java Development: http://www-106.ibm.com/developerworks/java/jdk/
Sun JDO referenece implementation: http://access1.sun.com/jdo/
Implementations of j2ee:
Websphere, WebLogic, Jboss, Geronimo, etc...
And a lot of more documents.
That's the Question: Microsoft or freedom? Windows or freedom to select any SO?
You could use SOAP for communication between the "front" and "back" ends. The .NET front end would send a SOAP message to the j2ee back end which would respond with a SOAP message back to the .Net SOAP port. This would "componentize" your app and make the front end and back end independent of each other. SOAP is made for this kind of language independent communication.
The problem is that it is going to slow you down. You have to parse xml left and right.
As far as .NET is concerned, I think Van Halen put it best...Running with the devil.
Well, I'm not sure why anyone would like to use both technologies...
I would use Java because it has proven to be a good and quite stable solution for years; .NET is still a newer technology which forces you to the Microsoft platform. I would certainly use .NET for projects that are changing often and are NOT critical for business processes, so the ease of use will help you a lot, but for critical business processes where a failure in the server (let's not say the code, let's talk about Windows) might cause you trouble, I would certainly use a 100% Java based solution.
Regarding your question, I would not recommend to use mixed solutions; if you get them to work, you will be bound to certain packages, software or whatever you have to use to do it, and you will loose portability.
What were you planning to use to communicate java with .NET? Were you expecting to put both on different servers/platforms?
I have worked with C backend and a Java Front communicated with Tuxedo, and all I can tell you it's a mess. If one technology offers you the stability, speed and reliability you need, why would you brake your head to mix up different stuff?
Wow ... didn't realise that there are many replies to my old thread ... have been busy with all the projects.
The good news is, all projects are finally implemented using JAVA-based apps.
Even managed to convince other team to cross over to JAVA with ease.
Thanks for all the comments guys ... maybe too late a reply but certainly not too late to say that Java leads the way!
Happy with this combo now: JBoss + Tomcat + Expresso Frmwrk + Oracle.