21242: ALF-2879: XAM Connector changes
- Fixed setting of store name
- Added properties:
- xam.archive.retentionPeriodDays=0
- xam.archive.addLock=true
21244: ALF-2879: Updated readme.txt
21262: ALF-3611 - tweak AVM orphan reaper test (PurgeTestP)
21277: Fix ALF-889 - WCM/AVM folder disappears when cut-and-paste into itself
- fixed cycle check before rename/move
- added -ve unit test
- externalized existing cycle error messages
21284: ALF-2879: XAM Connector changes
- Listen to store selector policies (incl. workaround for policy listening)
- Set XAM retention (code is setting the value, but not successfully tested against test servers)
21285: StoreSelectorPolicies.OnContentMovedPolicy is deprecated. Use StoreSelectorPolicies.AfterMoveContentPolicy.
- Deprecated so old policy still exists and works
- Will remove for 3.4 (maybe)
21293: Fix ALF-3245: stream not closed in DictionaryBootstrap.onDictionaryInit()
21303: ALF-2879: XAM Connector changes
- Throw ContentIOException if setBaseRetention fails
21313: ALF-2879: XAM Connector changes
- Round ms to nearest second
- Log actual ms value being set for retention
21322: Fix AVMNodeService.createNode to close output stream and avoid "Too many open files" (also add example AVMFileFolderPerformanceTester)
21331: ALF-2879: XAM Connector changes
- Removed duplicate setting of base retention
- Left code hooks for setting of other metadata
21368: Merged V3.3 to V3.3-BUG-FIX
21213: Merged DEV/TEMPORARY to V3.3
21200: ALF-2978: IMAP cannot bind to all the interfaces (0.0.0.0)
“imap.server.host” property can be used for setting IP address / network adapter to listen on for IMAP protocol.
21219: Merged PATCHES/V3.2.1 to V3.3
21216: ALF-3779: A few bug fixes to --FOREACH handling in SchemaBootstrap
- New system.upgrade.default.batchsize property to control overall default batch size
- Added in a few more missed --FOREACH markers
21211: ALF-3779: Remaining scripts converted to use --FOREACH (as logs finally provided by test prove that they need it too!)
21210: (RECORD ONLY) Incremented version label
21209: ALF-3779: Solution to allow batching of mass updates in upgrade scripts into smaller transactions
- A special preceding comment in this format specifies a numeric table column to control the batching and a global property specifying the batch size
--FOREACH table.column batch.size.property
- If the property isn't specified in alfresco-global.properties, the default batch size is 10,000
- INSERT / UPDATE / DELETE statements can then tack on extra conditions on ${LOWERBOUND} and ${UPPERBOUND} variables. E.g.
WHERE n.id >= ${LOWERBOUND} AND n.id <= ${UPPERBOUND}
- The statements are substituted and executed for each batch range up to the maximum value of the column
- 2.1 and 2.2 MySQL upgrades reimplemented this way
21207: Extra debug logging to track index triggering activity
21295: Merged HEAD to V3.3
21255: Parameter encoding
21298: Merged V3.2 to V3.3
21297: ALF-3889: JBPMDeployProcessServlet is now disabled by default and enabled with this in alfresco-global.properties
system.workflow.deployservlet.enabled=true
21317: dod5015: Parameter encoding
21363: Merged PATCHES/V3.2.1 to V3.3
21338: (RECORD ONLY) Incremented version label
21335: ALF-3779: Correction to error in --FOREACH range restriction for UPDATE statement
21290: ALF-3960: ArrayIndexOutOfBoundsException when we set mergerMergeFactor > mergerTargetOverlays
21278: (RECORD ONLY) Merged PATCHES/V3.1.2 to PATCHES/V3.2.1
21264: ALF-3889: JBPMDeployProcessServlet not accessible by default
- Should only be enabled in development environment
21364: Merged PATCHES/V3.1.2 to V3.3 (RECORD ONLY)
21264: ALF-3889: JBPMDeployProcessServlet not accessible by default
- Should only be enabled in development environment
21365: Merged PATCHES/V3.2.0 to V3.3 (RECORD ONLY)
21276: Merged PATCHES/V3.1.2 to PATCHES/V3.2.0
21264: ALF-3889: JBPMDeployProcessServlet not accessible by default
- Should only be enabled in development environment
21366: Merged PATCHES/V3.2.r to V3.3 (RECORD ONLY)
21279: Merged PATCHES/V3.1.2 to PATCHES/V3.2.r
21264: ALF-3889: JBPMDeployProcessServlet not accessible by default
- Should only be enabled in development environment
21367: Merged PATCHES/V3.3.1 to V3.3 (RECORD ONLY)
21343: Incremented version label
21342: ALF-3997: Merged V3.3-BUG-FIX to PATCHES/V3.3.1
20623: Fix for ALF-3188 : Access Denied when updating doc via CIFS
21282: Merged PATCHES/V3.1.2 to PATCHES/V3.3.1
21264: ALF-3889: JBPMDeployProcessServlet not accessible by default
- Should only be enabled in development environment
21239: Created hotfix branch off ENTERPRISE/V3.3.1
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21369 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
11008: FileFolderService no longer uses Lucene
11014: Fixed ETWOTWO-569: Regression after ContentStoreCleaner overhaul
11021: Fixed HibernateSessionHelperTest
11028: Fixed unit test's expected values
11035: Made cm:auditable optional and fixed 64K limit on property list sizes
11038: IncompleteNodeTagger handles aspects that are not in the dictionary
11039: Added tests to ensure that QName caching is case-insensitive
11040: Fixed use of mixed-case QNames for aspects
11044: Allow background AND in-transaction indexing to be disabled at the same time.
11046: Removed Lucene use from RegistryServiceImpl
11050: Removal of Lucene usage
- ML services finding root using XPath moved to path query
- RepoStore now uses simple path query
- Remove unused imports on PersonServiceImpl
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@11215 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
10561: Merged V2.2 to V2.9
9882: Node DAO separation
10580: Merged V2.2 to V2.9
10576: Missing onContentDelete firing
10577: More policies: beforeCreateNode and beforeDeleteNode when archiving nodes in hierarchy
- Updated UsageService and TenantService to conform to the new node DAO (more separation)
- TODO: Tenant node interceptor not present. This must be added if Multi-Tentant features are required.
- NodeMonitor event processing now checks that the nodes are still valid before processing.
- onMove firing was breaking NodeMonitor. Changed onMove to not fire when nodes are moved between stores.
- Raised ALFCOM-1912: ClassCastException when accessing property of type ver2:versionNumber
- Pull setFixedAcls fully into Node DAO for simpler and speedier execution
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@10709 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
9845: Merged V2.2 to V2.9
9733: Merged V2.1 to V2.2
9281: Improvements to index AUTO recovery
9316: Fixed ETWOONE-193: Transactional caches not being cleaned up after rollback (2.1.4 regression)
9317: Fixed ETWOONE-194: Faster void handling during index tracking
9365: Improved performance for finding which snapshots have been indexed
9413: Support to retrieve read/write state of the transaction and ensure Lucene commits are handled last
9414: ACT-3245: Updating node properties and aspects don't bump the alf_node.version value
9415: Code cleanup: Removed unnecessary empty methods
9416: Fixed creation of multiple thread pools
9417: Full index recovery absorbs indexing exceptions by default
9418: Added AUTO index recovery option to sample in line with Wiki docs
9419: ETWOONE-194: Index tracking is too slow
9420: Fixed ETWOONE-201: Better logging and configurability for RetryingTransactionHelper
9421: Fixed ETWOONE-202: SPlit person cleanup doesn't break read-only transactions
9422: Follow up on CHK-3317: Removed use of JDK 1.6 NavigableMap interface
9423: Fixed unit test after CHK-3317
9424: More test fixes after CHK-3317
9425: Ensure that index tracking tests don't run too long.
9426: Made concurrent reindexing optional. It is on by default.
9509: ACT-3539: Mid-transaction locking on Lucene resources
9547: Multithreaded index tracking startup: Handle previously lagging single-threaded rebuilds
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@10592 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
svn merge svn://svn.alfresco.com:3691/alfresco/BRANCHES/V2.0@5141 svn://svn.alfresco.com:3691/alfresco/BRANCHES/V2.0@51352 .
- FLOSS
- Some files will need a follow-up
-root/projects/repository/source/java/org/alfresco/repo/avm/wf/AVMRemoveWFStoreHandler.java (not yet on HEAD: 5094)
-root/projects/repository/source/java/org/alfresco/filesys/server/state/FileStateLockManager.java (not yet on HEAD: 5093)
-onContentUpdateRecord (not on HEAD)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@5167 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
VersionCounterDao is enclosed in non-propagating transactions (via config)
version_counter row is locked while version number is incremented
Added tests to ensure failure before fixing
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@2646 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
Extended <mandatory> definition in the DD.
The "mandatory" properties in our system have, until now, been optional, i.e. the integrity has not been enforced.
It is possible to have
<mandatory enforced="true">true</mandatory>, which means "mandatory and enforced", but
<mandatory enforced="false">true</mandatory>, which means "mandatory but not enforced".
Our system properties have been marked as "mandatory".
Dublin core has had the properties marked as "required". Currently, if the Dublin Core is added, the node is tagged with sys:incomplete.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@2562 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
