The de-lucening work has already moved to the required pattern where a check for container existence should be performed rather than just creating it, this allows GET requests to be declared to use a 'readonly' transaction which in turn provides performance benefits as more caching can be done. These webscripts have therefore been marked as 'readonly' in their descriptor, a few doclib scripts also work without code changes so have been marked as readonly too.
I've added a new unit test (org.alfresco.repo.web.scripts.ReadOnlyTransactionInGetRestApiTest) that calls all scripts mentioned in the JIRA issue immediately after creating a site (meaning there are no containers present) as we identify more scripts that need the same treatment they can be added to this test.
To help identify other GET webscripts using 'readwrite' transactions i've added a log WARN to RepositoryContainer which will output the following in the server console:
2011-09-21 08:57:46,431 WARN [web.scripts.RepositoryContainer] [main] Webscript with URL '/alfresco/service/slingshot/doclib/treenode/site/readOnlyTestSite/documentLibrary' is a GET request but it's descriptor has declared a readwrite transaction is required
I'll suggest that QA raise new bugs when they see these and we can prioritise individually, we can disable this warning before release if necessary.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30664 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
