6 Commits

Author	SHA1	Message	Date
Kris McQueen	41a16a478a	Fixes required for regressions found running automated tests. (1) method signatures that weren't properly refactored to new API framework (2) API request parameter types should always be specified lest they default to String which may or may not be desired (3) better exception handling with regard to Queued commands and generic exceptions (4) fix eventing to pass the proper accountId where neccessary	2010-10-01 14:11:18 -07:00
Kris McQueen	95a7f20a0a	Adding in XML response serializing. Now the new API framework supports both XML and JSON responses the way the old framework did.	2010-09-28 17:36:27 -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	f4caf145c3	Refactoring dispatching API commands from the scheduled async job. Instead of calling an executor, the dispatcher invokes the method on the manager directly. After the command is executed the response is serialized to the async job table so it can be queried later. Also serialize a response for async create commands that includes the id of the object being created.	2010-09-13 18:28:19 -07:00
Kris McQueen	88395cfcd8	CreatePortForwardingService has been refactored to the new API framework. CreatePortForwardingServiceRule has also been refactored to the new API framework. This is the first async create command, so there are some changes for the framework with async creates. First, the annotation has a 'createMethod' element, the framework will invoke the createMethod synchronously, update the id of the created object, return the jobId and objectId, then queue the method. Once the method is invoked the actual business logic will kick in, for example 'createVolume' will create a database record for the volume, return the appropriate id, and then asynchronously create the volume in the correct storage pool. The requirement is now that both a create method and an implementation method will be required in the given manager for async create commands.	2010-08-18 19:06:12 -07:00
Manuel Amador (Rudd-O)	ac730ec496	Branch 2.1.refactor committed	2010-08-11 09:13:42 -07:00