- NOTE: this fix means that any existing publishing channels in the repo will cease to work and will cause the publishing generally to have problems. If you have publishing channels in your repo then you must remove them following this fix. This can be done by either cleaning your repo out completely or deleting the node underneath "Data Dictionary/Publishing Root" (it has a UUID as its name).
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30646 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
The new TestNotificationProvider acts like a simple callback. You inject an instance of the new NotificationReceiver into the above NotificationProvider and then override the EMailNotificationProvider with the test one.
By doing so, emails will not be sent, but the NotificationContext object, which encapsulates all input state for such emails, can be stored and validated against expected values.
Test code for same.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30618 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
30520: Revisited timestamp propagation (cm:modified) now that the system does this by default
- Original low-level code (Hibernate optimizations) pulled back into NodeService implementation
- Use case driven prompting to touch the parent node
- Full indexing and policy callbacks against parent (was missing completely)
- Optimizations to ensure parent node modifications are only done where required and
the same transaction is used where possible
- 1s accuracy limit is maintained to prevent unnecessary modifications
- Enhanced tests to cover use cases where propagation is expected
- ALF-10262: Timestamp propagation is enabled by default
- Fixes or will fix:
- ALF-10291: Test disabled: SOLRTrackingComponentTest (various)
- ALF-7433: A file deleted using the web UI still appears in a NFS mount but with NULL stats
- ALF-10271: Test disabled: ArchiveAndRestoreTest.testAR7889ArchiveAndRestoreMustNotModifyAuditable
- ALF-10267: Test disabled: NodeServiceTest.testArchiveAndRestore
Also
- Found problem where cm:auditable properties could be modified directly against the cached values
- Extended locking of cached entities to the AuditablePropertiesEntity
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30598 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
o Alfresco key store manages keys and backup keys internally
o moved key registration and checking into AlfrescoKeyStoreImpl
o encryptor thread cache fix resulting from reload of key stores at runtime
o more encryption and key store tests
o tidy up + more comments
o moved hard-coded values to properties file
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30405 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
- there is now a "noindex" index subsystem
- has debug for all methods - method called and args
- has trace - adds call stack
log4j.logger.org.alfresco.repo.search.impl.noindex.NoIndexIndexer=fatal
log4j.logger.org.alfresco.repo.search.impl.noindex.NoIndexSearchService=fatal
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30403 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
A new property "system.workflow.jbpm.definitions.visible" has been added, set to false by default. This means that when the JBPM engine is enabled (the default for upgrades) in-flight workflows can continue but the JBPM definitions will not be returned and therefore hide them from the UI preventing new instances from being created.
If customers want to show the JBPM workflows again all is required is to set the "system.workflow.jbpm.definitions.visible" property to true.
The Workflow MBean has also been updated to expose the new property and the Workflow admin console now displays the value.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30356 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
30321: ALF-10115: Working copies in repository upgraded to 4.0 does not get cm:original association - breaks document listing
In WorkProvider.getNextWork() method, changed type of results to Set<Pair<Long, NodeRef>>
to prevent duplicate nodes in the returned collection.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30322 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
- Timestamps don't propagate during store move because the source node
is always deleted and therefore disappears
- Fixed ALF-10201: Test disabled: ChannelServiceImplIntegratedTest
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@30284 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
