Build applications better, faster, and cheaper with Nexaweb.

COMPATIBILITY OF NEXAWEB WITH JBOSS

DLT Solutions, Inc. and Nexaweb Technologies can help you leverage your JBoss infrastructure to build Ajax and RIA applications. If you are a JBoss user, and you are interested in utilizing Struts, Spring and server-side frameworks other than JSF to deploy Ajax and rich Internet applications, take a few minutes to learn about Nexaweb, and the Nexaweb Enterprise Web Suite.

Benefits of using Nexaweb:

• It’s simple, structured, and easy to maintain: Building dynamic mission-critical RIAs, composite, and enterprise mashup applications using Ajax, Java, Flash, Swing, and other client-side technologies that access internal, external and 3rd party data is simple, structured, and easy to maintain.
• It doesn’t require re-writing code because it’s done in a unified declarative XML development environment.
• Nexaweb works seamlessly with the J2EE environment.
• Platform can be completely integrated into any J2EE infrastructure.
• The Nexaweb Platform, which is offered through DLT Solutions, has been tested and deployed on all of today’s most popular J2EE application servers, including JBoss, among others.
• Nexaweb and DLT offer the solutions that help you do it faster, better, cheaper.

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 More

   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 More

   Make your agency more efficent by leveraging an end-user device’s processing power to display the application. This means that server load is decreased and that each server can support more end users.

3. Client-side Library More

   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, which will save you and your agency a lot of time!

J2EE Integration

Nexaweb has several J2EE resources that must be deployed to take advantage of the full functionality of the Platform. Applications are not required to deploy the Nexaweb Enterprise Data Services (EDS) in order to utilize the Nexaweb Universal Client Framework. However, for applications that need real-time messaging, declarative binding to Web services and databases, clustering and application monitoring, Nexaweb’s EDS are required. Deployment of Nexaweb’s Enterprise Data Services are handled just like any other J2EE framework deployment. Nexaweb’s J2EE resources must be added to the “web.xml” file and EDS Java libraries need to be placed in the Web application. Nexaweb makes this process easy for your organization using two tools:

1. Nexaweb Studio More

   Save time by automatically deploying Nexaweb into J2EE projects during the project creation process. Nexaweb Studio will also manage the process of upgrading the Nexaweb Platform and deploy the application to standard J2EE server through its integration of Eclipse’s Web Tools Project.

2. “Nexawebify” More

   “Nexawebify” is an ant task that allows developers to integrate Nexaweb into applications at build time. The Nexawebify task handles the injection of web.xml tags needed to run Nexaweb as well as the deployment of all Nexaweb resources in their correct locations. Using Nexawebify will make it easy to upgrade Nexaweb and reduce the complexity of adding Nexaweb to your application.

Once deployed, the developers can integrate Nexaweb functionality into their application using configuration files and API’s specific to server development. Deployment of Nexaweb will not interfere with an existing application. This allows developers to migrate sections of an application over to the Nexaweb Platform incrementally or run a Nexaweb application and HTML application side-by-side.

Resources:

• Leverage J2EE when building Enterprise Web 2.0 Applications

Articles:

• AJAXWorld: Nexaweb Hails Mashups
• Refining the Art of Enterprise Web Apps