Slashdot Mirror

← Back to Stories (view on slashdot.org)

Building A J2EE App with Linux

Posted by Hemos on from the build-'em-and-run-them dept.

Dejected @Work writes "If you think "Hello World" is always simple and boring try building it with a entity/session EJBs, a servlet, a JSP page, and a HTML home page on Linux. This tutorial shows you how to develop, test, run, and debug a complete J2EE application using Linux and WebSphere(trial download)."

3 of 32 comments (clear)

  1. j2ee and linux: the killer combo by tps12 · · Score: 4, Interesting

    This tutorial is an excellent starting point for people who want to get into J2EE. J2EE has quickly become one of the hottest new technologies on the market, and for good reason.

    Some background for n00bs: J2EE == Java 2 Enterprise Edition, Java's flagship Java product. Ironically, "Java 2" actually refers to Java >= 1.2, but we'll let that slide. ;) In any case, the enterprise edition has proven the favorite environment for high-availability, low-latency business applications.

    As for deployment platform, I have to say that Linux is the ideal Java platform. Both companies support open source, so the community has made sure the integration is tight and optimized for users that demand the performance of C++ with the ease of use of Python.

    This tutorial would be of help to anyone trying to break into the software industry, and a boon especially to those interested in C# and .NET, which by all appearances will be to Java what Java was to Linux, minus X11 and plus COM.

    --

    Karma: Good (despite my invention of the Karma: sig)
  2. Re:J2EE overkill by Anonymous Coward · · Score: 1, Interesting

    amen. I've seen too much of this lately. I'm starting a project using J2EE, and the only components of it that I'm using are EJB, JMS, and JTA. The other stuff I'm filling in with Apache and PHP.

  3. Linux/J2EE Scalability Problem for Enterprise Apps by lprimak · · Score: 3, Interesting

    Unfortunately, Linux is not an adequate deployment platform for high-traffic enterprise apps. This is due for the most part to the Linux threads architecture (or lack thereof) and less-than-optimized java implementation. Since Linux has no real threads and no optimized mutex locking (such as adaptive locks), high workload, simultaneous requests and network traffic brings latencies up very rapidly and makes the system dog slow very quickly.

    Of course, Linux can be a great development platform for J2EE, and the apps can be deployed on Solaris (even Solaris Intel) or MacOS X (which has a marveous super-optimized JVM)

    In (clearly unscientific) testing that I made, Solaris Intel was about 3x as fast under load and a lot snappier than Linux on the same hardware.

    --
    Lenny Primak PP-ASEL-IA,Heli