Regression 3.0.1 vs 2.15.3: client external Ingest #41
Assignees
Comments
|
Il n'y a aucun erreur de ce type avec 2.15... donc pas de log... |
|
Merci pour avoir scindé les issues. |
|
OK, même constat que pour DIP (Access External Client): changement de comportement fonctionnel du client Java lors d'une erreur 500 En 2.15, le log produit: En 3.0.1: Donc même cause même effet: un changement du comportement du client produit une incompatibilité entre la version 2 et la version 3 pour un client de Vitam. Je vais voir de mon côté pour rendre mon programme "tolérant" à cette incompatibilité ascendante (si je peux). |
|
Pour info, je rechigne à corriger mon code pour prendre en compte ce changement majeur car:
Changement important, n'est-il pas ? 404 est aussi du coup une erreur Exception, et ainsi de suite... Changer un retour normal par une exception qui, de plus, est déjà utilisée pour d'autres cas d'erreur, rend plus complexe la gestion des erreurs pour un client externe (comment fait il la différence entre une erreur temporaire et une erreur définitive, une erreur du client interne et une erreur du serveur externe) ? Que proposez-vous ? |
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Apr 22, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam.
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Apr 22, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam.
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Apr 22, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars:* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6 * org.apache.httpcomponents:httpclient-cache:jar:4.5.7
|
Note: pour le moment, le fix n'est que temporaire et ne sera sans doute pas "validé" comme merge, c'est plus pour vous montrer les impacts... |
|
Bonjour Frédéric, |
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Apr 23, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Apr 23, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
|
Certes, mais du coup, c'est un retour en arrière (contrat de fonctionnement). Du coup, il est impossible de prendre en compte des statuts différents de réponse du serveur et donc de traiter ces erreurs différemment. Ceci est un problème grave selon moi. |
|
La norme Vitam était VitamError pour permettre de gérer les différents cas et de réserver les exceptions aux cas purement interne sans solution côté usager. Ici vous avez oublié ce point et donc c'est selon moi une régression sévère et non un bug fix. Certains pourraient dire que c'est une nouvelle feature, mais ce ne serait qu'un joke ;-) |
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Jun 24, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Jun 24, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Jul 4, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Jul 4, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Jul 8, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
|
Il semble que la 3.0.3 ne fixe pas ces points. Je me trompe ? |
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Jul 15, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Sep 4, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Sep 15, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Sep 30, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to fredericBregier/WaarpVitam
that referenced
this issue
Sep 30, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
fredericBregier
added a commit
to waarp/WaarpVitam
that referenced
this issue
Sep 30, 2020
This version of Waarp-Vitam is compatible with Vitam 2.15.3 and 3.0.2. This is a short fix for Change Behavior from Vitam client side. It should not get any issue for Waarp-Vitam users but we follow this issue with Vitam Team. See ProgrammeVitam/vitam#41 and ProgrammeVitam/vitam#42 Note that this module is compiled against Java 8, thus allowing anyone to use it with Java 8, 9, 10, 11 and follow, so with Vitam 2.15 and Vitam 3.0. Vitam jar are not include in the all dependencies jar anymore to counter-act the Java 11 issue from Vitam side, letting final users to choose between Java 8 and above and V2 of Vitam OR Java 11 and above and V3 of Vitam. However we work with Vitam team to get a Waarp version available for both versions 2 and 3. Note that the "all jar" versions does not include any more the Vitam jar, in order to allow you to use either v2.15.3 or v3.0.1 and following versions. You therefore need to ass the following jars with the Waarp-Vitam library: **Common Jar for both V2 and V3 versions of Vitam** *Vitam jars:* * fr.gouv.vitam:ingest-external-client * fr.gouv.vitam:common-public-client * fr.gouv.vitam:ingest-external-api * fr.gouv.vitam:access-external-client * fr.gouv.vitam:common-public * fr.gouv.vitam:common-http-interface * fr.gouv.vitam:access-external-api * fr.gouv.vitam:common-database-public **Specific to V2 version of Vitam** *Vitam jars:* * fr.gouv.vitam:access-external-common:jar:2.15.3 * fr.gouv.vitam:logbook-common-client:jar:2.15.3 * fr.gouv.vitam:logbook-common:jar:2.15.3 *Other jars: Those jars are included by default, even if Vitam V3 does not need them (no issue).* * com.github.fge:json-schema-validator:jar:2.2.6 * com.googlecode.libphonenumber:libphonenumber:jar:6.2 * com.github.fge:json-schema-core:jar:1.2.5 * com.github.fge:uri-template:jar:0.9 * org.mozilla:rhino:jar:1.7R4 * javax.mail:mailapi:jar:1.4.3 * net.sf.jopt-simple:jopt-simple:jar:4.6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Découpage en deux Issues sur les deux clients
Cette erreur n'arrive pas en 2.15.3, mais arrive en 3.0.1:
Cause probable:
où le code async a été changé en profondeur...
Mon code s'inspire très fortement des tests Junit de Vitam pour le client Ingest External Rest et y intègre simplement un outil intermédiaire (waarp) qui fait appel au client Ingest External Rest.
En V2.15, aucun soucis (comme avant 2.11, ...). Mais en 3.0.1, le code Junit se plante dans le check du client external, sans que quoi que ce soit semble différent entre le code Junit v3.0 et V2.15 de Vitam sur ce point:
https://github.com/ProgrammeVitam/vitam/blob/master_3.0.x/sources/ingest/ingest-external/ingest-external-client/src/test/java/fr/gouv/vitam/ingest/external/client/IngestExternalClientRestTest.java
The text was updated successfully, but these errors were encountered: