Currently the Persistence module autoloads with MitkCore. This can lead to potentially problematic behaviour. Additionally, as it is not in general use there is no need to autoload. Instead modules which need it should state their dependencies.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Wontfix | None | T18265 Remove dependency to mitk persistence module which should be auto loaded | ||
| Resolved | None | T18369 Remove persistence autoload functionality |
Event Timeline
Comment Actions
[e5d8e1]: Merge branch 'bug-18369-do-not-autoload-persistence'
Merged commits:
2014-10-28 17:09:13 Caspar Goch [3bf5d9]
Remove autoload
Comment Actions
uhm is there any report about the "problematic behaviour"
autoloading is for sure the best way to integrate this into the application. otherwise one will need a static method or direct instatiaation of the service class.
should be a temporary solution. the other way would be to integrate the whole system into the MitkCore since it only needs PropertyLists and TinyXML....
Comment Actions
be advised that removing autoloading does not remove the shared library from the autoload folder (if this was not changed so far)
thus, to avoid problematic behaviour again one will need to remove it manually
Comment Actions
Alfred and I will take a look tomorrow to verify whether removing the autoloading fixed the problems he experienced. I removed the autload today so we get feedback from the nightly dartclients before bugsquashing.
Comment Actions
[2f34e7]: Merge branch 'bug-18369-adapt-test'
Merged commits:
2014-10-31 15:29:22 Caspar Goch [1e93ea]
Adapt test