AutoFirma ins and outs (4). Errors in tests in afirma-core, jmulticard-jse

 1. The package org.xml.sax is accessible from more than one module: <unnamed>, java.xml and TestMIMEDetection failure

This error is produced in the afirma-core project to solve the error in TestMIMEDetection. At fist to solve it, the "Apache xerces" dependecy is added to the build.gradle,

In StackOverflow explains that a package is both in the Modulepath and in the Classpath. The ModulePath is the jdk or jre that is being used and the Classpath is formed by the libraries that are imported. Usually, the packages that begin with "java." or "javax." cannot be included in the Classpath as they should be in the jdk. In the menu option "Configure build path" you can see this option.



The dependencies in the build.gradle are:

api libs.jmimemagic

api libs.xerces

The library that has conflictive dependencies is "xerces". 

To solve this problem in Gradle click on "Project and External Dependencies" to see the libraries. 

Here are two views, the first without the "xerces" lib and the second with the "xerces" lib



In the next image, you can see that "xml-apis" has been added by the "xerces" lib. That includes the conflictive  "javax." packages.



Now the build.gradle file should be as follows. Note the highlighted code.
dependencies {
    testImplementation libs.junit
    
    api libs.jmimemagic
    api libs.xerces 
}

configurations { // @see: https://stackoverflow.com/a/59294690/7704658
   all*.exclude group: 'xml-apis'
}

Now the TestMIMEDetection is not failing!

2. TestCeres430Signature, TestDnieSignature, failures (jmulticard-jse project)

If you don't have the DNIe installed, this test will fail. So comment on the code of this test! 

3. TestJseCryptoHelper failure (jmulticard-jse project)

I don't know the cause of the problem of this test. So I will comment on the code


Now if you run 

./gradlew build 

there are no problems

Comments

Post a Comment

Popular posts from this blog

ORVE WS (Dynamic) (4) Jackson XML mapper

0. Introduction I love Jackson parser as it is easy to use and can be used to with some data formats such as CSV ,  JSON , YAML and XML . Just define a wrapper and a class for marshalling/unmarshalling. Although JAXB is a standard, in the Java ecosystem exists many solutions. And my decision is to use Jackson. 1. Defining MAVEN dependencies To use Jackson XML it is required this dependency in Maven. Note that  ${jackson.version} represents a variable that contains preferably the latest Jackson version. 1 2 3 4 5 <dependency> <groupId> com.fasterxml.jackson.dataformat </groupId> <artifactId> jackson-dataformat-xml </artifactId> <version> ${jackson.version} </version> </dependency> But if you want to use CSV, JSON or YAML in the project, it is as easy as including these dependencies 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 <!-- Jackson for CSV --> <de...
Read more

ENI (1) ENI Document OR the Spanish Electronic Administration Mafia

Image
0.Introduction. Getting the "xsd" schemas 1. Obtaining the afirma.xsd 2. Managing the "xsd" schemas. Changing  schemalocation  property from the  xsd  tag 3. Generating classes from xsd schema 4. Modifying the classes to solve operational problems 0. Old version 1. Generating the classes 0.Introduction. Getting the "xsd" schemas To obtain the correct URLs of the schemas: 1.For the document: https://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e in this URL it is shown these schemas (click on the link and download the schemas): http://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e/documentoEni.xsd http://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e/metadatos/metadatosDocumentoEni.xsd http://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e/contenido/contenidoDocumentoEni.xsd http://administracionelectronica.gob.es/ENI/XSD/v1.0/firma/firmasEni.xsd 2. For the file (expediente) https://administracionelectronica.gob.es...
Read more

ORVE WS (Dynamic) (12) Defiining the control tables

0. Introduction Our goals are: Retrieving the INPUT records (Received from other administrations) Retrieving the OUTPUT records (Sent to other administrations) To retrieve any record the WS requires at least these parameters   1. State (Estado). For INPUT these are the available states: RPC : Received but confirmation pending RR : Received and rejected RC : Received and confirmed RREEN : Received and resent      For OUTPUT : PE : Pending delivery EPC : Sent but confirmation is pending ER : Sent but rejected EC : Sent and confirmed 2. Date from in " YYYY-MM-DD HH:MM:SS " format 3. Date to in the same format. The system knows who is our administration (Oficina or Office) 1. Additional tables or entities We need to have control of: "Ids" that can identify the records and if the records have been saved and passed to the Gexflow application (an application that controls our records). To get the "Ids", the WS operation...
Read more