Hi Martin: 1. The different being that XAP reduces the need of writing and maintaining Javascript - using XML instead. XML is dynamically processed on the client side and rendered. Using Kabuki, developers need to write Javascript code. Both are valid approaches for writing apps, they address different developer preferences - in general, reducing the amount of Javascript that needs to be written is a good thing for developers.
More technical information and examples can be seen at: http://www.nexaweb.com/open/xap (This is a URL created specifically for XAP for providing additional background information); 2. With XML, it is easy to integrate Ajax power with MyFaces or Portal. For example, it is fairly straightforward for server JSF code to send out XML instead of HTML, which would be rendered by XAP on the client side to create rich UI. This enables developers to leverage the power of MyFaces or other server side framework for rich web app, without dealing with a lot of Javascript. Some JSF tags abstracts such issues out on the server side - in XAP, it follows the same idea but does the processing on the client side. Regards, ---Coach -----Original Message----- From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: Thursday, May 04, 2006 6:51 AM To: MyFaces Development Subject: Re: Proposal idea for Declarative Ajax project Hi, this sounds interesting, I haven't quite understood though what the difference to AJAX toolkits such as Kabuki would be. Can you - on the level of source code - explain me the difference? You talk about XML versus JavaScript for UI representation, what would this mean in an example? regards, Martin
