DWR Java Proxy Framework for AJAX Data Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional 3-layer Web application development architectures, particularly with AJAX enabled systems, face challenges in data conversion and transfer between the browser, server, and backend systems, making extension and maintenance complicated and time-consuming.
Innovation Solution
An extended enterprise connector framework is introduced, utilizing a Java proxy generated at the Web server as a mid-layer, which communicates with the frontend client via DWR, allowing direct access to the Java proxy using AJAX, thereby simplifying data conversion and enabling rapid development and maintenance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional 3-layer Web application architecture with AJAX is used, then rich UI functionality and better user experience are achieved, but data conversion and transfer work between browser, server, and backend system becomes complicated and time-consuming
Solution Approach 1:
The patent introduces a mid-layer with Java proxy beans that act as an intermediary between the AJAX engine and the enterprise backend system. This mid-layer encapsulates the complex data conversion logic, providing a simplified interface for both the frontend JavaScript and backend RFC modules, thereby resolving the contradiction between rich UI functionality and data conversion complexity
Solution Approach 2:
The patent segments the Web application architecture into distinct layers: frontend Web presentation layer, mid-layer with Java proxy beans, and backend enterprise system. This segmentation allows each layer to handle specific responsibilities independently, with the mid-layer specifically managing data conversion, thus reducing overall system complexity while maintaining rich UI capabilities
2Adaptability or versatility
If AJAX technology is implemented for rich UI functionality, then granular UI event propagation to server is enabled, but extension and maintenance work becomes very complicated and time consuming
Solution Approach 1:
The Java proxy beans in the mid-layer serve as an intermediary that simplifies extension and maintenance by providing a standardized interface. When extending functionality, developers only need to modify the proxy layer rather than dealing with complex AJAX and backend integration details, thereby maintaining granular UI event propagation capability while reducing extension and maintenance effort
Solution Approach 2:
The patent performs preliminary action by pre-configuring the mid-layer with Java proxy beans that encapsulate common data conversion patterns and backend communication protocols. This preliminary setup provides a reusable framework that simplifies future extension and maintenance work while preserving AJAX's granular event propagation capabilities
3Productivity
If DWR is used to communicate with enterprise backend system, then AJAX Web site development is enabled, but significant amount of data conversion between frontend and backend must be performed
Solution Approach 1:
The patent merges the data conversion functionality directly into the mid-layer Java proxy beans, combining the AJAX communication handling and backend data conversion in a single integrated layer. This eliminates the need for separate data conversion steps, thereby maintaining AJAX Web site development capability while reducing data conversion time
Data Source
AI summary
Techniques for extended enterprise connector framework are described herein. According to one embodiment, a Java proxy is generated in a form of Java beans at a Web server as a mid-layer, using an enterprise connector. The enterprise connector provides object oriented classes that encapsulate specific function calls of a Java connector which represents a set of proprietary APIs (application programming interfaces) to access RFC modules of a backend enterprise system. A JavaScript proxy is generated for a frontend client that communicates with the Web server over the Web using a DWR (direct Web remoting) mechanism to allow the JavaScript proxy to directly access the Java proxy of the mid-layer via an AJAX (asynchronous Java and extensible markup language or XML) communication mechanism, where the JavaScript is invoked by a Web application of the frontend client at runtime. Other methods and apparatuses are also described.