JJAX - Framework for Enterprise AJAX Applications

JJAX builds on Google's GWT by providing a framework for building secure database driven applications using the full power of AJAX and Java OO programming. JJAX provides basic features that allow programmers to be more productive while enabling the construction of enterprise scale web applications.

Full Power of AJAX and Java Together

JJAX builds on GWT by providing a framework for building secure database driven applications. JJAX provides basic features that allow programmers to be more productive. Some of the key features of JJAX include:

• Secure and authenticated access to GWT applications and RPCs. Build one or multiple application modules and decide which RPC calls each application has secure access to.
• JJAX does not try to replace the components in GWT, but instead offers higher level components that make programmers more productive and extends GWT to enterprise web applications.
• Efficient lazy loading support in major containers such as tab panels, deck panels, stack panels and other high-level widgets. Lazy loading allows for efficient construction of large applications with little complexity. You can build your views and decide later if a view is lazy loaded, destroyed on hide, or refreshed when revisted. JJax uses a simple IoC pattern to achieve this which gives programmers a lot of flexibility with minimal complexity.
• Very handy bread crum GUI feature including bread crum trail containers that allow for advanced navigation without a lot of programming effort. All the hard lifting for managing state and navigation is done by the framework. Often times when building navigation from view to another view implementing return button or back button features can lead to messy code. JJax has built in support for managing GUI state and bread crums.
• Easily make blocking and non-blocking RPC calls.
• Easily chain multiple RPCs together in much the same way you call a single RPC without any special logic.
• Blocking RPC calls suspend GUI actions with optional "is processing" message. "Is processing" GUI is customizable.
• When you upgrade the GWT/JJAX client (fix a bug or add a new feature), you can optionally force end users to load the new client version into thier browser. For example, this can be necessary if there is a serious bug that requires users to upgrade their GWT client immidiately or if the client upgrade is required to synchronize with a corresponding server change that impacts API compatiability in the RPCs. With this feature the server hosting administrator controls if the end user needs to upgrade their GWT client (even if they are in an active session).
• Build larger applications in a modular fashion using multiple entry points. This an optional feature for very large applications, and it gives you the ability to easily build multple entry points into your application and thus reduce the javascript download size and without any complex change to your code. This essentially gives you the option of breaking up a large application into multiple javascript files instead of the typical single gwt download while still having a single outer entry point that manages overall application structure.