incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Coach Wei" <co...@nexaweb.com>
Subject RE: XAP (Extensible Ajax Platform) Proposal
Date Thu, 18 May 2006 18:35:01 GMT
Noel:

Thanks for the comments. Very well put about what you would like to see
XAP become - I see the same thing as well. I'd like this project to be
as successful as possible with precisely the goal you quoted.  I don't
think it would be as successful as it could be if it stayed tied to its
Nexaweb roots.  One of the reasons of proposing this project at Apache
is to bring in all those other good ideas with a broad dev and user
community to keep it going.

For example:
On 5/18/06, Craeg Strong <cstrong@nyc.saic.com> wrote:
> For me, I would like to see added the ability to employ XSLT on the 
> server side to pre-generate DHTML pages from XAP page templates, 
> especially for initial page loads.
I think this is a good suggestion. This can be done and it would work
well with XAP. 

Regard to the question of "Where is the binding for client events
connecting to the server-side model, be it tying into a JSF framework or
binding to a WSDL-defined service?":
1. Client events connect to server side resources via normal HTTP
request/response to a server side URL. As a result, server side can be
JSF, JSP, Servlet, ASP, ASP.NET or just pure static pages. 
2. Dojo and Kabuki all provide ways to connect to server side via SOAP
or JSON like interface - such things would be supported by XAP as well. 

-----Original Message-----
From: Noel J. Bergman [mailto:noel@devtech.com] 
Sent: Thursday, May 18, 2006 1:50 PM
To: general@incubator.apache.org
Subject: RE: [VOTE] XAP (Extensible Ajax Platform) Proposal (was XAP
(Extensible Ajax Platform) Proposal)

+1

I would also like this project to grow beyond its Nexaweb origins, and
try
to add best of breed ideas taken from such other products as Adobe Flex
and
Google Web Toolkit, neither of which is Open Source, to further the goal
of
being "an
open source framework for building and deploying rich internet
applications
independent of browsers and servers."

One thing that I don't see, reviewing http://www.openxal.org/.  I read
that
it "is a pure client-side implementation. It should support any server
side
infrastructure", but I don't see how it connects UI elements to the
server-side infrastructure.  Where is the binding for client events
connecting to the server-side model, be it tying into a JSF framework or
binding to a WSDL-defined service?

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message