AjaxSwing is a web-based deployment platform that runs Java Swing applications. It permits companies that developed Java Desktop applications to deploy them as web applications.
AjaxSwing is a platform for deployment that automatically converts Java Swing and AWT applications to AJAX web-based applications at the time of execution. It can be described as a runtime Java conversion HTML converter that can convert Java desktop programs to web-based applications. AjaxSwing is distinctive in that it needs virtually no changes to existing applications and does not require developers to learn any API other than the AWT/Swing API. It can function as the Thick Swing client or as a browser-based thin AJAX RIA, giving dual client solutions to Java. This lets companies leverage the time and resources to develop Swing applications while enjoying the advantages of using thin-client deployment. For a complete list of features, check out this page on Features.
Many clients have used our application since 2000. Most of them were capable of converting the application in less than an entire week. Conversion is an easy process that involves installing AjaxSwing and creating an AjaxSwing configuration file. Application.
Java application can be integrated into the AjaxSwing platform in under 30 minutes. CreamTec Professional Services can assist in the deployment process or product modification and assure that all application features are working in AJAX mode. All this at a very reasonable cost.
Migration of Java desktop apps to the internet
To show how the software is used, the screenshots below illustrate how an example Java Swing application looks in the browser when it is installed within AjaxSwing. The left side of the images illustrates an active GUI program (the source). On the right side, the application is run by AjaxSwing, and windows are represented as pages displayed in the browser.
Companies that have invested years of development and hundreds of millions of IT budgets to build the Swing user interfaces face an essential decision. They can continue to build using Swing and deploy with WebStart, which requires client-side maintenance and is not a genuine thin client.
