Automatically convert Java desktop application to web application

AjaxSwing converts Java desktop applications to web applications at runtime. Every standard component of Swing is rendered as AJAX component in the browser and user events are emulated back to the Swing application running on the server. This approach allows building dual-client user interfaces in Java because the same code base can run as a GUI desktop application and as browser-based web application.

Companies that has invested years of development time and hundreds of thousands of IT budgets into building Swing user interface have a tough decision to make. They can continue to develop using Swing and deploy using WebStart, which requires client-side maintenance and is not a true thin client. Modern user demands a thin client so this path is not a long term solution. The other choice is to rewrite the user interface from scratch using J2EE and an AJAX framework such as Google Web Toolkit (GWK), Yahoo User Interface Library (YUL), AJAX-enabled JSF or a set of open source components. While this path has long term advantages, it requires a heavy investment of time and resources into rebuilding what the company already has, and due to the lack of standards there is no clear choice on which AJAX framework to use.

AjaxSwing provides a natural migration path for Java desktop applications by providing automatic conversion to AJAX. Virtually without modifications the existing Swing based front end can be deployed as a thin client. Our product supports every standard Swing component by providing an AJAX version that runs in the browser. Take a look at our demos to see how AjaxSwing renders tables, trees, tabbed panes and dialogs. It’s an amazing technology that has made our clients hugely successful because they were able to convert their Java Swing applications to AJAX websites in just a few days or weeks. The big advantage is that using AjaxSwing relieves the developer from having to learn HTML, JavaScript and AJAX. Use the following links to get more information.

<< back to Solutions