Alex Huang 4807bc8bda Added a config to enable checking whether a db transaction is wrapped around communications with the agent. If it is, an exception is thrown. This assert has actually been there because it is part of CloudStack's design principle to not use db transactions as a way to enforce atomicity in executing things on hardware resources. However, the assert has been ignored since the move to maven which is not good with enabling asserts. Since then, there's been a lot of commands added that actually runs within db transaction. This is a big no no as the problem is that the remote operation may take a long time and the db can actually close the connection, causing a rollback of the transaction. We should not depend on transactions to enforce the atomicity anyways.		2014-03-26 13:35:31 -07:00
..
api	CLOUDSTACK-5432: potential bugs in case of stop mgt server while	2014-03-26 14:55:21 +01:00
components-api	CLOUDSTACK-6247: Usage Events - hide them when display flag is off in the context of "Ability to have better control over first class objects in CS" feature	2014-03-17 18:50:06 -07:00
network	Reformat of source code to set a stable base for the future. I couldn't get checkstyle enabled. There's still about a thousand errors from checkstyle. Most of it from length errors from comments and strings. Will attempt to remove those tonight. This change is so large I just want to get it in before any merge nightmares. The changes are fairly minor though and I did a full compile and start a server with the reformat code.	2013-11-21 07:56:47 -08:00
orchestration	Added a config to enable checking whether a db transaction is wrapped around communications with the agent. If it is, an exception is thrown. This assert has actually been there because it is part of CloudStack's design principle to not use db transactions as a way to enforce atomicity in executing things on hardware resources. However, the assert has been ignored since the move to maven which is not good with enabling asserts. Since then, there's been a lot of commands added that actually runs within db transaction. This is a big no no as the problem is that the remote operation may take a long time and the db can actually close the connection, causing a rollback of the transaction. We should not depend on transactions to enforce the atomicity anyways.	2014-03-26 13:35:31 -07:00
schema	CLOUDSTACK-5432: potential bugs in case of stop mgt server while	2014-03-26 14:55:21 +01:00
service	Moved security out into its own jar. Will be adding more to it. Fixed a few white space issues brought up by checkstyle in eclipse.	2014-01-09 16:12:25 -08:00
storage	checkstyle: unused import removed	2014-03-26 15:37:54 +01:00
pom.xml	Slight optimization, don't run checkstyle on container or non-java projects.	2014-02-18 12:24:11 +01:00