5 Commits

Author	SHA1	Message	Date
Kris McQueen	2a4ddac41a	Change getResponse() to return a ResponseObject so that the caller can choose how to serialize. This in in preparation for serializing the async commands to the database with class information and deserializing them into the ResponseObject itself when queryAsyncJobResult is called. Once the ResponseObject is deserialized, the proper string can be returned to the caller. ... The previous behavior had the JSON response from the command embedded into the queryAsyncJobResult response as a string rather than a JSON object which prevented the client from being able to read the response. With this new behavior an actual JSON object should be returned which can then be parsed on the client side.	2010-09-23 17:34:28 -07:00
Kris McQueen	e2e0e76063	More work on serializing responses. Now responses have to have the name set on them, and the name will eventually be serialized to the JSON/XML response the way it used to work for commands themselves [the result of cmd.getName() was written to the response string]. For list respones, we wrap the individual objects in a ListResponse object that has the name of the response, and the individual objects have the object name so that accounts will be something like <listaccountsresponse><account><...></account><account><...></account></listaccountsresponse>.	2010-09-17 17:13:04 -07:00
Kris McQueen	e6ebe3ac77	Refactoring listServiceOfferings to new API framework.	2010-09-07 17:29:13 -07:00
Manuel Amador (Rudd-O)	ac730ec496	Branch 2.1.refactor committed	2010-08-11 09:13:42 -07:00
Manuel Amador (Rudd-O)	05c020e1f6	Source code committed	2010-08-11 09:13:29 -07:00