yeah, nobody really uses soap for ajax, it's all about json now...
soap is really more for backend to backend systems, whereas ajax pretty much expects displayable or near-displayable data for the purpose of human consumption.
in practice, soap is just too much to use as a decent client/server interchange.
wsdl is a nice idea given the state of heterogeneous jsonp apis, but the fact remains that it hasn't really taken off in the js community.
there are not great xml tools for JS. jQuery has some, plus a lot of ajax tools that will help you get started.
i would forget about the wsdl and just worry about interfacing with the php on an as-needed basis defined by your apps needs.
BROWSER STATS [% share]
(2013/10/31) IE7:0.5, IE8:8.6, IE9:5.3, IE10:12.3, FF:17.7, CH:41.8, SF:8.1, MOBILE:20.4
Last edited by rnd me; 04-04-2012 at 05:35 PM..