Newsletter sign-up
View all newsletters

Enterprise Java Newsletter
Stay up to date on the latest tutorials and Java community news posted on JavaWorld

Gunning for Sun

Enhydra 3.52 serves up an affordable, multitiered alternative to the J2EE application development approach

  • Digg
  • Reddit
  • SlashDot
  • Stumble
  • del.icio.us
  • Technorati
  • dzone
J ava can be used many ways in Web applications, from the simple, old-fashioned CGI to the complex J2EE (Java 2 Enterprise Edition) framework. With help from the open-source community, Lutris Technologies has developed Enhydra, a unique, pure-Java framework for enterprise Web applications.

Enhydra is a collection of open-source Java projects made commercial by the addition of Lutris' documentation, code samples, and support. These added benefits are worth the scant investment -- 95 per CPU, as compared to J2EE fees of as much as 5,000 per CPU -- if you buy into Enhydra's approach to Web applications. Lower-cost alternatives to J2EE can only do the market good, but at the same time, it is reasonable to question the long-term wisdom of adopting any enterprise Java framework but J2EE.

We tested Enhydra 3.52 on a server with dual Intel Xeon CPUs and 256MB of RAM. Being pure Java, Enhydra runs wherever Java does; we chose Red Hat Linux 7.1.

This latest Enhydra release updates Java compatibility to Java Developer's Kit Version 1.3, adds graphical application creation wizards, enhances the InstantDB Java database, extends support to wireless applications, and strengthens the Kelp development toolset.

To appreciate Enhydra 3.52's uniqueness, you should understand how Sun constructs Web applications. In Sun's Java servlet model, a Web server passes HTTP requests from users to the Java servlet responsible for the requested information. The servlet parses the user's request, interacts with databases and back-end systems as needed, and produces the dynamic Web page that's displayed in the user's browser. An extension of servlets, JSP (Java Server Pages) uses HTML and XML templates to shape the application's output.

Servlets and JSP work very well, but they have been criticized for failing to steer developers toward creating tiered applications. A servlet can be, but notably, need not be, monolithic, performing data access, business logic, and presentation formatting in the same source code file. In contrast, Enhydra forces a sharp delineation between an application's presentation and business tiers. Enhydra developers can work independently on business logic and presentation code (in this case, HTML), freeing each developer to focus on his or her strongest skills. Enhydra weaves the separate tiers together at run time.

The key to Enhydra is Lutris' XMLC (XML compiler). Instead of marking HTML and XML documents with special tags that let a presentation engine such as JSP know where to insert data, a developer working with XMLC creates an ordinary, static HTML or XML document that's displayable on any browser. XMLC digests the document and creates an object model that the Java developer uses to produce a dynamic presentation. Aside from being easier to use than JSP and facilitating the advantageous separation of development roles, XMLC extends its capabilities to all HTML/XML dialects, including wireless variants such as WML (Wireless Markup Language) and cHTML (compact HTML).


  • Digg
  • Reddit
  • SlashDot
  • Stumble
  • del.icio.us
  • Technorati
  • dzone
Comment
Login
Forgot your account info?
Add comment
Anonymous comments subject to approval. Register here for member benefits.
Have a JavaWorld account? Log in here. Register now for a free account.
Resources