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
..
executor	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.	2010-09-23 17:34:28 -07:00
AsyncCommandQueued.java	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
AsyncJobExecutor.java	cleaning up imports, fixing up some compilation problems related to API refactoring	2010-09-13 15:25:46 -07:00
AsyncJobExecutorContext.java	API refactor	2010-08-18 11:24:29 -07:00
AsyncJobExecutorContextImpl.java	API refactor	2010-08-18 11:24:29 -07:00
AsyncJobManager.java	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
AsyncJobManagerImpl.java	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.	2010-09-23 17:34:28 -07:00
BaseAsyncJobExecutor.java	cleaning up imports, fixing up some compilation problems related to API refactoring	2010-09-13 15:25:46 -07:00
SyncQueueManager.java	cleaning up imports, fixing up some compilation problems related to API refactoring	2010-09-13 15:25:46 -07:00
SyncQueueManagerImpl.java	cleaning up imports, fixing up some compilation problems related to API refactoring	2010-09-13 15:25:46 -07:00