Skip to content
This repository has been archived by the owner on Jun 26, 2021. It is now read-only.

Handling of relative proxy uris #90

Open
hallvard opened this issue Sep 19, 2016 · 0 comments
Open

Handling of relative proxy uris #90

hallvard opened this issue Sep 19, 2016 · 0 comments
Labels
Milestone

Comments

@hallvard
Copy link
Contributor

I think I've discovered an issue in proxy uri handling. If there is a relative uri in an emfjson file and the reference.isResolveProxy() is true and type != null the referenced object is not resolved, yet, but instead a proxy object (of the indicated type) is created. This is as it should be. But the proxy uri that is stored in the object is the same relative uri, but I think it should be a resolved absolute uri. If not, it won't resolve correctly later. I took a look at XMLHandler and it seems to resolve the uri against the referencing object's resource uri, before storing it in the proxy.

@ghillairet ghillairet added the bug label Sep 23, 2016
@ghillairet ghillairet added this to the 1.0.0-RC1 milestone Sep 23, 2016
ghillairet added a commit that referenced this issue Oct 5, 2016
Resolved URI before creating a proxy
@ghillairet ghillairet modified the milestones: 1.0.0, 1.0.0-RC1 Nov 18, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants