Mechanism for Developing AJax Applications Using Java Swing Framework and Method for Using the Same

• US 20080127217A1
• Filed: 09/05/2006
• Published: 05/29/2008
• Est. Priority Date: 09/05/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Wang, Anping
• Granted Patent: US 7,861,213 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

In one embodiment, a mechanism makes use of AJax to enable Swing applications deployable as Internet applications that runs on a J2EE server. The mechanism enables an application developer to develop and deploy Swing applications to the J2EE server while providing users with the equivalent of a Rich Internet Application (RIA). The mechanism builds a bridge between a browser event model and a server resident Swing UI event model.

Claims

1. For web applications, a mechanism comprising:

an AJax enabled application for capturing an event from a Swing panel;

a client resident event controller for transferring the event to a server;

a rendering engine for building a document object model based on renderings received from the server; and

a DOM event model for re-rendering a client view of the Swing panel.

2. The mechanism of claim 1 further comprising an input device for selecting a portion of the web page to initiate an event.

3. The mechanism of claim 1 wherein the event comprises a JavaScript event.

4. The mechanism of claim 1 wherein the AJax enabled application is a browser.

5. The mechanism of claim 1 further comprising:

a server resident Swing application;

an action controller for receiving an event from the client resident event listeners;

a Swing model for determining the context of the event and for associating the event with one of a plurality of server resident event controllers;

a server resident Swing application controllable by the sever resident event controllers; and

a plurality of renderer kits for rendering the output of the Swing application back to the rendering engine when a change in the display of the Swing panel occurs.

6. The mechanism of claim 5 further comprising a session manager for identify the source of the event.

7. The mechanism of claim 5 further comprising a tooling platform for developing the Swing panel.

8. The mechanism of claim 5 further comprising an integrated development environment (IDE).

9. The mechanism of claim 8 wherein the IDE comprises a Java IDE adapted to develop and deploy the Swing panel.

10. A method for executing a Swing application deployed on a server from a client resident application, the method comprising:

capturing an events from a client resident application;

transferring the event to a server side Swing application;

at the server side, locating a Swing component that is responsible for the event;

invoking the Swing event model to call registered listeners; and

re-rendering a user interface if required.

11. The method of claim 10 further comprising providing a tooling platform for developing a Swing panel.

12. The method of claim 10 further comprising providing an integrated development environment for developing a Swing panel deployable on a J2EE server.

13. The method of claim 10 further comprising providing a Java integrated development environment adapted to develop and deploy a Swing panel.

14. For a web application, a mechanism for developing and deploying a Swing panel, the system comprising:

a Swing application displayed on an application server;

a client side AJax enabled browser for accessing the Swing application;

means for detecting user selections at the browser and passing the selections to the server; and

means for rendering the output of the Swing application at the browser.

15. The system of claim 14 further comprising a integrated development environment for designing and deploying a Swing panel.

16. The system of claim 14 wherein the detecting means comprises an event controller for passing Javascript events to the application server.

17. The system of claim 14 wherein the rendering means comprises a set of render kits.

18. The system of claim 17 wherein the output of the render kits is passed to a client side AJax rendering engine and converted to a Document Output Model (DOM).

19. A machine-readable medium including instructions executable by one or more processors, the machine-readable medium comprising:

one or more instructions for displaying a Swing application to an application server;

one or more instructions for accessing the Swing application from a client resident application and to transparently pass user input to the application server; and

one or more instructions for updating user input (UI) status and render back to the client resident application.