10 Commits

Author	SHA1	Message	Date
alena	1a6d78eae4	Code cleanup. No need to declare runtime exceptions (CloudRuntimeException, InvalidParameterException, PermissionDenied exceptions)	2011-04-21 16:26:53 -07:00
alena	e4765fb32b	bug 6969: return jobId/jobStatus for IpAddress and SecurityGroup as ids for these objects were introduced in 2.2.x	2011-02-22 09:09:55 -08:00
alena	6f55c4dd7e	bug 8270: Synchronize on 1) ipAddress object when create/delete ipForwarding/portForwardingRule and vpn service 2) on networkId when assignTo/removeFrom/deleteLoadBalancer ... status 8270: resolved fixed	2011-02-03 18:45:49 -08:00
alena	026e6905c9	bug 8343: in api commands extending BaseAsyncCreate set owner account information only after all request parameters were read as account/domainId information can be specified in the request ... status 8343: resolved fixed	2011-02-03 09:53:18 -08:00
will	c67d26cec4	bug 6969: First step of now displaying pending async jobs for listXXXCommands. There is a lot more cleanup and fixing to do but all commands acting against VirtualMachines now work.	2010-11-30 19:12:09 -08:00
alena	cb74030d01	bug 7298: throw an Exception when invalid job Id is specified in queryAsyncJobResult ... status 7298: resolved fixed	2010-11-23 15:06:29 -08:00
alena	1c24deda34	1) Refactored current Apis not to use reflection for method invocation. In new version following has to be done: ... * Implement callCreate() and execute() methods in apis extending BaseAsyncCreateCmd (example - CreateVolumeCmd) * Implement execute() method in apis extending BaseCmd and BaseAsyncCmd (example - deleteVolumeCmd and deleteUserCmd) We no longer need createMethod(), method(), manager() fields in @Implementation annotation, cleanup has to be done. 2) Moved Account/User related methods to AccountManagerImpl. Methods are exposed via AccountService interface. 3) Enhanced exception handing for Api calls. 4) Created ConfigurationService interface, all Api config methods are exposed via it.	2010-11-08 11:27:36 -08:00
Kris McQueen	3f6a438d92	Refactoring the AsyncJobManager to queue jobs appropriately if there is a need to synchronize execution on an object, e.g. a router. API developers can now call command.synchronizeCommand(String, Long) to force the command to be synchronized on a particular object type [the string arg] with a particular id [the long arg]. When synchronizeCommand() is invoked, an exception maybe thrown by the framework (AsyncCommandQueued exception) to force the business logic to abort. The command will then be queued and invoked at the appropriate time. The synchronizeCommand() is re-entrant and will be a no-op if the command has already been queued and is now ready for execution.	2010-09-16 19:05:06 -07:00
Kris McQueen	df10af0688	cleaning up imports, fixing up some compilation problems related to API refactoring	2010-09-13 15:25:46 -07:00
Manuel Amador (Rudd-O)	05c020e1f6	Source code committed	2010-08-11 09:13:29 -07:00