bug #5095
closed
Fix failing dozer related tests
Added by Cherian Mathew almost 9 years ago.
Updated over 3 years ago.
Description
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,
eu.etaxonomy.cdm.remote.dto.assembler.lsid.AssemblerTest.testSpeciesProfileModelMapping
eu.etaxonomy.cdm.remote.dto.assembler.lsid.AssemblerTest.testLazyInitializationExceptionWithProxy
eu.etaxonomy.cdm.remote.dto.assembler.lsid.AssemblerTest.testDeepMapping
eu.etaxonomy.cdm.remote.dto.assembler.lsid.AssemblerTest.testLazyInitializationExceptionWithPersistentCollection
eu.etaxonomy.cdm.remote.dto.assembler.lsid.AssemblerTest.testSimpleDarwinCoreMapping
eu.etaxonomy.cdm.remote.dto.assembler.lsid.AssemblerTest.testOAIDublinCoreMapping
eu.etaxonomy.cdm.remote.view.OaiPmhViewTest.testGetRecordView
eu.etaxonomy.cdm.remote.view.OaiPmhViewTest.testRdfGetRecordView
eu.etaxonomy.cdm.remote.view.OaiPmhViewTest.testListIdentifiersView
eu.etaxonomy.cdm.remote.view.OaiPmhViewTest.testListRecordsView
eu.etaxonomy.cdm.remote.view.RdfViewTest.testNameInformationRdf
This needs to be fixed urgently as it prevents the deployment of the cdmlib jars to the maven repository.
Added @Ignore to the tests for now (r25125) for building the taxeditor urgently for Sabine.
- Target version deleted (
Release 3.8)
moving unresolved tickets to next milestone after release of 3.8.0
- Target version deleted (
Release 3.12)
- Target version changed from Release 4.0 to Release 4.1
- Target version changed from Release 4.1 to Release 4.2
- Target version changed from Release 4.2 to Release 4.3
- Target version changed from Release 4.3 to Release 4.4
- Target version changed from Release 4.4 to Release 4.5
- Target version changed from Release 4.5 to Release 4.6
- Target version changed from Release 4.6 to Release 4.7
- Target version changed from Release 4.7 to Release 4.8
- Target version changed from Release 4.8 to Release 4.9
- Target version changed from Release 4.9 to Release 4.10
- Description updated (diff)
- Target version changed from Release 4.10 to Release 4.12
- Target version changed from Release 4.12 to Release 4.13
- Target version changed from Release 4.13 to Release 4.14
- Target version changed from Release 4.14 to Release 5.0
- Precedes task #7286: re-enable dozer related tests added
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
- Private changed from Yes to No
- Target version changed from Release 5.0 to Release 5.1
- Target version changed from Release 5.1 to Release 5.2
- Target version changed from Release 5.2 to Release 5.3
- Target version changed from Release 5.3 to Release 5.5
- Target version changed from Release 5.5 to Release 5.6
- Target version changed from Release 5.6 to Reviewed Next Major Release
- Related to bug #6324: fix dozer mapping after removal of synonym relations and after using TaxonNode added
- Status changed from New to Resolved
- % Done changed from 0 to 50
- Subject changed from URGENT : Fix failing dozer related tests to Fix failing dozer related tests
- Assignee changed from Andreas Müller to Andreas Kohlbecker
- Target version changed from Reviewed Next Major Release to Release 5.21
- 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.
- Status changed from Resolved to Closed
- Target version changed from Release 5.21 to Release 5.20
I fixed the variable name.
http://memory.loc.gov testing is not part of this ticket therefore I close this ticket. Please open a new one if you think http://memory.loc.gov testing should be handled in a ticket.
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.
Also available in: Atom
PDF