eXo-JCR-jcr

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

    • -0
    • +13
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 4 more files in changeset.
JCR-2312 : use the same dialect variable for jcr and lock

JCR-2312 : use the same dialect variable for jcr and lock

    • -13
    • +0
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

    • -0
    • +13
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
  1. … 4 more files in changeset.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

    • -0
    • +13
    /exo.jcr.component.core.impl.infinispan.v5/pom.xml
JCR-2311: Datasource added

    • -5
    • +5
    /exo.jcr.component.core.impl.amazonaws.v1/pom.xml
JCR-2311: First version

    • -0
    • +829
    /exo.jcr.component.core.impl.amazonaws.v1/pom.xml
    • -0
    • +19
    /exo.jcr.component.core.impl.amazonaws.v1/src/test/resources/test.policy
  1. … 8 more files in changeset.
JCR-2308: Fixed the typo

JCR-2307: Reverted the code reformat and fixed the typo

JCR-2310: First step

    • -0
    • +541
    /exo.jcr.component.core.impl.tokumx.v1/pom.xml
  1. … 13 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-322 : Document the behavior of restoreIdentity param - SetCurrentIdentityFilter

JCR-2290 : TestQuotas.testQuotaWhenWorkspaceIsRemoved fails randomly on Mysql

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

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

JCR-2292: JCR-2309 Avoid replication for local changes

JCR-2288: JCR-2309 Avoid replication for local changes

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-2288: [Cluster] Adding nodes to the same parent node causes TimeoutException

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

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

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-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

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

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