Fix failing dozer related tests
Dozer related tests are failing due to missing dtd file,
java.io.IOException: Server returned HTTP response code: 503 for URL: http://dozer.sourceforge.net/dtd/dozerbeanmapping.dtd
The failing tests include,
This needs to be fixed urgently as it prevents the deployment of the cdmlib jars to the maven repository.
ref #5095 avoid running dozer tests when dozer.sourceforge.net is not available
#19 Updated by Andreas Kohlbecker over 3 years ago
the tests in
cdmlib-remote/src/test/java/eu/etaxonomy/cdm/remote/dto/assembler/lsid/AssemblerTest.java cdmlib-remote/src/test/java/eu/etaxonomy/cdm/remote/view/OaiPmhViewTest.java cdmlib-remote/src/test/java/eu/etaxonomy/cdm/remote/view/RdfViewTest.java
have been disabled.
Solve the original problem and remove all @Ignore
#30 Updated by Andreas Kohlbecker 9 months ago
- Assignee changed from Andreas Kohlbecker to Andreas Müller
- % Done changed from 50 to 100
code changes look good, test are all successful so the ticket is solved and can be closed.
I am a bit concerned though that we could run into a situation where the oai server is absent permanently (
oahServerURI = new URI("http://memory.loc.gov"); <-- typo here in var name, should be oaiServerURI). The server at this URI seems to be quite old and may be replaced completely at some day?
Therefore we should consider using server mocks instead.
#31 Updated by Andreas Müller 9 months ago
- Status changed from Resolved to Closed
- Target version changed from Release 5.21 to Release 5.20
I fixed the variable name.
Generally we already planned to test availability of required external services via a test not running together with cdmlib testing but separately do avoid cdmlib is failing if some service is temporarily not availabe. This still needs to be implemented.