On Tue, Jun 12, 2012 at 6:48 AM, Sanjiva Weerawarana <[email protected]>wrote:
> Yes but that's the limitation we need to fix! Its not too hard .. its > recursive application of the same rules :). If we can solve it that way, then it would be ideal. Anyway, I didn't get the exact idea behind the solution. If I consider a payload like [1] for the operation "saveUser", did you mean something like below. saveUser(getUserInfo(username, birthday, getAddress(addressLine1, addressLine2, city, country))); If it is not, can you please provide a sample method signature, then I can better understand. At the same time, we also need to come up with a convention to map service names/type names etc. to JS function names. [1] <userInfo> <username/> <birthday/> <address> <addressLine1/> <addressLine2/> <city/> <country/> </address> </userInfo> -- *Ruchira Wageesha Senior Software Engineer & Member, Management Committee, Development Technologies* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: [email protected], blog: ruchirawageesha.blogspot.com, mobile: +94 77 5493444*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
