ERGO PROGRESS 0809 4CT
Activities performed
- none.
Outcomes and results
- none.
Problems and concerns
- none.
Plans for next period
- This WP has been completed
Activities performed
- Most of the work has been directed to re-factor the persistence layer of the ebRR. The main reason to do this was the unsatisfactory performance caused by the rather complex queries that the Hybernate engine generates from the data access object model. This was a drastic decision, but its was based on query tests that we manually produced outside of Hybernate on the database. With the re-factored persistence layer we can control exactly how to build the queries and are confident that we reach a satisfactory query performance.
- There's work done on a Java client API to access the ebRR, but there's more work to be done on a Java API that connects directly with the core registry (needed for Toolbox integration).
Outcomes and results
- Improved persistence layer.
- Java Client API to access the ebRR
Problems and concerns
- The new persistence layer requires more testing.
Plans for next period
- More testing on the new persistence layer.
- Java API connecting to the core of the ebRR
Activities performed
- Activity is not yet started.
Outcomes and results
- none.
Problems and concerns
- none.
Plans for next period
- none