J2EE has been a staple of enterprise development for a long time. Whether you consider it bloated or difficult to work with, many enterprises have entrusted their mission-critical applications to the platform. There are many reasons for this - standards, vendor adoption, the number of frameworks, etc. Regardless of the reason, Nexaweb works seamlessly with the J2EE environment.

Nexaweb’s Platform can be completely integrated into any J2EE infrastructure. Out-of-the-box, the Nexaweb Platform snaps into any J2EE 2.3 Servlet Container by deploying a set of resources and API’s that developers can use to build next generation applications or migrate existing applications. The Nexaweb Platform has been tested and deployed on all of today’s most popular J2EE application servers including Tomcat, JBoss, Websphere, Weblogic, etc. Nexaweb’s seamless integration with J2EE is the result of Nexaweb’s commitment to standards. This technical brief covers each component of the Nexaweb Platform to provide a detailed explanation of how you and your development team can leverage your J2EE framework to build Enterprise Web 2.0 application with Nexaweb. .

Client-side Rendering
There are many architectural decisions that Nexaweb has made to make integration with a J2EE architecture possible, but none more important than Nexaweb’s client architecture. Nexaweb’s Universal Client Framework (UCF) is a set of three rendering engines implemented in two runtimes (Ajax and Java). All of Nexaweb’s clients work in the same way a Web browser works - they retrieve a file from the server and based on the Markup in the file, render the application by creating all the necessary components to display the application. Any additional resources (images, style sheets, data, business logic, etc.) which are necessary to complete the display are requested from the server and loaded into memory. Client-side rendering is a distinct advantage for Nexaweb and its customers for three reasons.

1. Use of any web-framework – Client-side rendering allows developers to use any web framework that can output text in the XML format of -all frameworks can do this. Other products that rely on server-side rendering such as JSF or Flex need to compile or down convert the markup on the server before sending it to the client. This means that in order to take advantage of the features of the product you have to work only within the framework. There are many web frameworks that have been created for J2EE (Struts, JSP/Servlets, JSTL, Tiles, Spring Webflow, JSF) and each one has features and benefits that make it a good choice for developers. Nexaweb’s architecture allows you to choose the feature from each that is best for you and use them within the Nexaweb Platform.
2. Leverage client-side processing – Leveraging an end-user device’s processing power to display the application means that server load is decreased and that each server can support more end users.
3. Client-side Library – Nexaweb’s UCF not only renders the client but gives developers a robust library to handle events, receive real-time data and update application state. The client-side library will handle the synchronization of data and client-side state with the server automatically. This gives the Platform the ability to perform one-way binding of data to user interface elements. With Nexaweb, if you change the data the UI will change automatically even if the data was changed on the server.

Download pdf Leverage J2EE when building Enterprise Web 2.0 Applications