{{ message }}
Repository navigation
EMFUtil.AbsoluteURIPreservingURIHandler should not be a singleton #157
Description
A URIHandler should not be a singleton as its baseURI field can be set. Consequently, when multiple load/save operations occur in different threads, the baseURI field could have the value of another resource, leading to an undesirable deresolve result.
Although this can be avoided using the "org.eclipse.emf.cdo.common.model.EMFUtil.CONVERT_TO_RELATIVE_URIS" property, I don’t think it should remain a singleton in any case.
Activity
claesrosell commentedon Apr 16, 2026
I have ran into this bug when we tried to upgrade to the latest version of CDO.
We have multiple meta-models with cross-references and the
readCDOPackageUnit()method ofCDODataInputImpl.javasimply fails to ready packages when multiple models are read at the same time.We to can avoid it by setting
org.eclipse.emf.cdo.common.model.EMFUtil.CONVERT_TO_RELATIVE_URIStotruebut I would really like to use the default behaviour since I suspect that the new model migration stuff works better with it.I will provide a PR for this
EMFUtil.AbsoluteURIPreservingURIHandler should not be a singleton ecl…
estepper commentedon Apr 17, 2026
Please give me a few days more to catch up with my backlog. I hope to find time next week...
EMFUtil.AbsoluteURIPreservingURIHandler should not be a singleton #157
EMFUtil.AbsoluteURIPreservingURIHandler should not be a singleton #157