Slashdot Mirror
Building A J2EE App with Linux
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)."
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.
;) In any case, the enterprise edition has proven the favorite environment for high-availability, low-latency business applications.
.NET, which by all appearances will be to Java what Java was to Linux, minus X11 and plus COM.
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.
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
Karma: Good (despite my invention of the Karma: sig)
And d/l the Java & J2EE SDK, run on Linux with Apache, Jakarta's Tomcat, JBoss, and use an open source DB like postgres or mySQL.
There are full open source options for J2EE (in fact, I have been toying the idea of making a weblogging program similar to slashcode or scoop with J2EE, under the GPL, of course).
And as a side note, J2EE on windows, linux, unix, or mac isn't different, you know. Did this article just get approved cause it has a tutorial in linux? The only thing that you'll have to deal with is installing the side software in linux (websphere, essentially).
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
The problem I see repeatedly with J2EE adoption is the insistence of developers to use every facet of the API. That means EJBs, JSPs, servlets, JMS (messaging), transaction services etc. People don't seem to realise that J2EE is a set of APIs, and a simple servlet/JSP/JDBC solutions is just as 'J2EE'-compliant as a full bean-driven, JTA-enabled solution.
To ease yourself in, start with servlets and JSP (obviously for web-enabled apps). Then start adding beans (stateless session then stateful session and then entity), etc. Don't hope to throw every Java-enabled TLA together and hope for a performant J2EE solution!