Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
JCR-2461 : make sure JCR namespaces used in tests exist (#55)

Some methods of the test class org.exoplatform.services.jcr.api.namespaces.TestNamespaceRegistry use namespaces created in the method org.exoplatform.services.jcr.api.namespaces.TestNamespaceRegistry#testQueryNsPropName.

If this method is executed after the others methods, the namespaces do not exist and the tests fail.

This fix registers at the beginning of each test method the namespaces used in the method to make sure they exist (if the namespace already exists, it is registered again).

    • -0
    • +4
    ./namespaces/TestNamespaceRegistry.java
JCR-2461 : make sure JCR namespaces used in tests exist

Some methods of the test class org.exoplatform.services.jcr.api.namespaces.TestNamespaceRegistry use namespaces created in the method org.exoplatform.services.jcr.api.namespaces.TestNamespaceRegistry#testQueryNsPropName.

If this method is executed after the others methods, the namespaces do not exist and the tests fail.

This fix registers at the beginning of each test method the namespaces used in the method to make sure they exist (if the namespace already exists, it is registered again).

    • -0
    • +4
    ./namespaces/TestNamespaceRegistry.java
Fix/jcr 2454 (#25)

JCR-2454 : Error JCR occured after delete a base version

    • -0
    • +132
    ./version/TestVersionHistory.java
  1. … 2 more files in changeset.
JCR-2416:Strange behavior of indexing rule (#26)

JCR-2416:Strange behavior of indexing rule & fix Incorrect excerpt for index aggregates

  1. … 5 more files in changeset.
JCR-2416 : Incorrect excerpt for index aggregates

  1. … 3 more files in changeset.
JCR-2454 : Error JCR occured after delete a base version

    • -0
    • +132
    ./version/TestVersionHistory.java
  1. … 1 more file in changeset.
JCR-2454 : Error JCR occured after delete a base version

    • -0
    • +132
    ./version/TestVersionHistory.java
  1. … 1 more file in changeset.
Squashed commit of the following:

commit ce87bce59d0a90e9c9b0d9a6856598a72302a21f

Author: bourasom <obouras@exoplatform.com>

Date: Fri Jun 24 10:57:04 2016 +0100

ECMS-7453: add unit test

commit 8db76d713537e2b3da4b9a2a4cd5fbe0b02b1dfb

Author: bourasom <obouras@exoplatform.com>

Date: Thu Jun 23 15:51:04 2016 +0100

ECMS-7453:XXE issue with xml data importing function of ecms

    • -0
    • +21
    ./importing/TestSystemViewImport.java
  1. … 1 more file in changeset.
ECMS-7453: add unit test

    • -0
    • +21
    ./importing/TestSystemViewImport.java
JCR-2450 : Speed up cache initialization

    • -0
    • +209
    ./core/query/lucene/ConcurrentQueriesWithUpdatesTest.java
  1. … 2 more files in changeset.
JCR-2450 : Speed up cache initialization

    • -0
    • +209
    ./core/query/lucene/ConcurrentQueriesWithUpdatesTest.java
  1. … 2 more files in changeset.
JCR-2450 : Speed up cache initialization

    • -0
    • +209
    ./core/query/lucene/ConcurrentQueriesWithUpdatesTest.java
  1. … 2 more files in changeset.
JCR-2433 : remove unit test.

JCR-2433 : Ability to disable the BloomFilter

    • -0
    • +109
    ./writing/JCRBugTest.java
  1. … 3 more files in changeset.
JCR-2432 : fix all javadoc errors raised by doclint (JDK 8)

    • -1
    • +1
    ./importing/TestImportVersionedChild.java
  1. … 580 more files in changeset.
JCR-2432 : fix all javadoc errors raised by doclint (JDK 8)

    • -1
    • +1
    ./importing/TestImportVersionedChild.java
  1. … 580 more files in changeset.
JCR-2432 : fix all javadoc errors raised by doclint (JDK 8)

    • -1
    • +1
    ./importing/TestImportVersionedChild.java
  1. … 578 more files in changeset.
JCR-2354 : Support Java 8

  1. … 1 more file in changeset.
JCR-2344: Parsing error appeared when export PDF file

    • -0
    • +221
    ./exporting/TestExportImport.java
  1. … 7 more files in changeset.
JCR-2343: Parsing error appeared when export PDF file and import it again

* Problem analysis:

An invalid character in a PDF file is stored in XML file when exporting it.

XML parser cannot then parse this character when importing again.

* Fix description:

- Validate all characters when exporting to System View.

If a string has invalid character, it uses Base64 encoding instead of unicode (default) for that string.

- When importing, it checks and sets appropriate encoding value per string.

- Nothing changes in case of Document View.

ECMS-6597 will provide a comprehensible message so that the user who imports such file can remove that character manually.

    • -0
    • +221
    ./exporting/TestExportImport.java
  1. … 7 more files in changeset.
JCR-2343: Parsing error appeared when export PDF file

    • -0
    • +221
    ./exporting/TestExportImport.java
  1. … 7 more files in changeset.
JCR-2341: Parsing error appeared when export PDF file

    • -0
    • +221
    ./exporting/TestExportImport.java
  1. … 7 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.

  1. … 5 more files in changeset.
JCR-2308: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

  1. … 5 more files in changeset.
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

  1. … 5 more files in changeset.
JCR-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

  1. … 5 more files in changeset.
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

  1. … 5 more files in changeset.
JCR-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

  1. … 3 more files in changeset.
Remove empty files

    • -0
    • +0
    ./core/query/lucene/IndexingQueueTest.java
  1. … 7 more files in changeset.
Remove empty files

    • -0
    • +0
    ./core/query/lucene/IndexingQueueTest.java
  1. … 7 more files in changeset.