Enterprise Application Integration (EAI) has been around for a decade. While EAI performs the integration at the back end, mashup is turning to an alternative to integrate the applications at the browser. A couple weeks ago, Simon Massey suggested me the introduction of the client-programming option in ZK 5.0 could make ZK an excellent solution for replacing the expensive and costly EAI and portal servers.
After a few experiments, I’m glad to share with you some of the results. However, it is more about how to provide a service ready for mashup with ZK, so I call it Ajax-as-a-Service.
In this post I’ll talk about how to mash up so-called Ajax-as-a-Service, and discuss some of the issues. The implementation will be discussed later in another post.
Mash Ajax-as-a-Service in a non-ZK page
aaase.chart.example1.Main. And, I hosted it on Google App Engine. To mash to a Web page, just specify the following in your Web page:
main parameter, and you can specify additional parameters if necessary.
In this example, we have specify the ID of the DOM element in the
id parameter to indicate where to place the ZK service.
Here is a complete example. You can save it as a HTML page locally and browse it.
Mash Ajax-as-a-Service in a ZK page
Mashing up the ZK service in a ZK page is similar, except both CSS and the ZK Client Engine are already loaded from the server serving the ZK page. Thus, it saves the network bandwidth by use of the following link:
Here is an example that shows two charts in two portal children.
Cross-site Scripting (XSS)