eXo-JCR-jcr

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
JCR-2332: The test case has been removed

[PLF-5989] Upgrade dependencies to next snapshots

[maven-release-plugin] [PLF-5989]prepare for next development iteration

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
[maven-release-plugin] [PLF-5989]prepare release 1.15.10-GA

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
[PLF-5989] Upgrade dependencies to latest releases

JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

Fix description:

- Relimit character number of a varchar field if dialect is mysql and utf-8

    • -0
    • +13
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 4 more files in changeset.
Revert "JCR-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists"

This reverts commit 0c627cd3979f90e8cfefff709d60f31a0fb7ce40.

COR-321 : Document the behavior of restoreIdentity param - SetCurrentIdentityFilter

JCR-2288: [Cluster] Adding nodes to the same parent node causes TimeoutException

Problem analysis

- The goal of this task is to get rid or limit the risk of getting TimeoutException when we concurrently add nodes to the same parent node in a cluster environment.

Fix description

- When we add a new child node, we have to invalidate the list of child nodes of the parent node in the cache which was done by a simple remove of the related cache entry. The problem with this approach is the fact that this remove was done in a global tx so when it is done concurrently we can face deadlock like in this particular use case. The fix simply isolates the invalidation by doing it outside the global tx in order to highly reduce the risk of such deadlocks. The second part of the fix ensures that if we do a local change, the related commands commit/rollback remain local because before the fix they were replicated even for local changes.

JCR-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

Problem analysis

* When the JCR checks if a mandatory property/sub node exists, it doesn't check for a specific item type such that if we have an existing item with expected name but not the expected type, we won't get the ConstraintViolationException as expected

Fix description

* We now check the name but also the type of the item

JCR-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

Problem analysis

- When the JCR checks if a mandatory property/sub node exists, it doesn't check for a specific item type such that if we have an existing item with expected name but not the expected type, we won't get the ConstraintViolationException as expected

Fix descripton

- We now check the name but also the type of the item

JCR-2306: Use a consistent snapshot version to avoid having to change pom file at each release

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
Merge remote-tracking branch 'origin/release/1.15.9-GA' into stable/1.15.x

    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
[PLF-5905] Upgrade dependencies to next snapshots

PLF-5684 : Declare the source release package used to bundle all PLF sources

Use argLine as POM property and not surefire configuration to be compatible with jacoco (Part 2)

    • -3
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
Use argLine as POM property and not surefire configuration to be compatible with jacoco (Used to retrieve tests coverage in Sonar)

[maven-release-plugin] [PLF-5905]prepare for next development iteration

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
[maven-release-plugin] [PLF-5905]prepare release 1.15.9-GA

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
[PLF-5905] Upgrade dependencies to latest releases

Remove empty files

JCR-2298: Collect the call stack on connection close only on debug mode

JCR-2296 : TestPermissions fails when the cache is disabled with single mode.

Problem analysis

- On the sjdbc mode, the id of ACLHolder contains the container name, this wrong format of UUID. It causes a wrong returned value at the storage level if the bloom filter is activated.

Fix description

- The UUID should not contain the container name.

[PLF-5750] Upgrade dependencies to next snapshots

JCR-2283: Cannot create new user on a preloaded database with 10 thousands of users

Fix description:

- Use loop instead of using recursive function.

[maven-release-plugin] [PLF-5750]prepare for next development iteration

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
[maven-release-plugin] [PLF-5750]prepare release 1.15.8-GA

    • -1
    • +1
    /applications/exo.jcr.ispn.ear/pom.xml
    • -1
    • +1
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 12 more files in changeset.
[PLF-5750] Upgrade dependencies to latest releases

JCR-2281: Loading all the properties into the cache causes undesirable side effects

Problem analysis:

- Some parts of the code (orderBefore + Remove + Same name sibling and import document view with UUID_COLLISION_REPLACE_EXISTING) could behave abnormally in case the cache contains all the properties of the target node, that is due to the fact that those parts of the code assume that we get the list of properties from the database which allows to have the correct path for the properties when we change the path of a node which is not true in case we get the list of properties from the cache because the path of the properties still have the old path.

Fix description:

- We make sure that the path of the properties matches with the expected/new path

  1. … 4 more files in changeset.
JCR-2270: Changes are not properly purged once indexed on slaves

Fix description:

- Purge change list on local cache of all cluster nodes.