Welcome to AjaxAnywhere
AjaxAnywhere is designed to turn any set of existing JSP or JSF components into AJAX-aware components
In contrast to other solutions, AjaxAnywhere is not component-oriented.
You will not find here yet another AutoComplete component.
Simply separate your web page into multiple zones, and use AjaxAnywhere to refresh only those zones
that needs to be updated.
How it works
The idea is simple:
Mark "reload-capable" zones of a web page with AjaxAnywhere custom tags.
During request processing on the server-side, determine the zones to refresh.
via AjaxAnywhere API.)
On the server-side AjaxAnywhere will generate an XML containing only the "updated" HTML.
difficult to debug and unit-test it in multi-browser environment. Get rid of all those
complexities by using AjaxAnywhere.
Easy to integrate. AjaxAnywhere does not require changing the underlying application code.
Lower technical risk. Switch whenever you need between AJAX and traditional (refresh-all-page)
behaviour of your web application. Your application can also support both behaviors.
Default graceful degradation. You do not need to develop another intreface for older browers
support. If XMLHttpRequest is not available, application will keep working in traditional way,
refreshing the entire page.
Free open source license.
Restrictions (price to pay)
AjaxAnywhere will probably cover your needs, to achieve certain functionality you might
- Today, you can only update a set of complete DHTML objects without breaking then apart. For example,
you can update a content of a table cell or the whole table, but not the last row, for example.
In later versions, we plan to implement partial DHTML update, as well.
Client-side scripts were tested on Microsoft Internet Explorer, Mozilla Firefox (both Windows and Linux), and Opera. Your help in cross-browser testing
it is also able to extract the declared functions into the proper context. (as if the page was
reloaded completely). However, it is impossible to execute document.write() command inside
The zones to reload might be known before submitting the request. In this case, override
side logic is necessary.