Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Importing Child Templates does not work #503

Closed
tomas-knap opened this issue Aug 16, 2015 · 1 comment
Closed

Importing Child Templates does not work #503

tomas-knap opened this issue Aug 16, 2015 · 1 comment

Comments

@tomas-knap
Copy link

Steps to reproduce:

  1. Under DPU templates, import one root DPU template (e.g., e-sparqlEndpoint).
  2. Copy such DPU template to create child DPU templates, name it somehow (differently from its parent)

screen shot 2015-08-16 at 12 15 07

3) export only the child DPU template (e-sparqlEndpoint 1 in this case) 4) delete e-sparqlEndpoint 1 from the tree 5) try to import previously exported e-sparqlEndpoint 1 6) As a result you got:

screen shot 2015-08-16 at 12 15 00

But such message is wrong, because you are NOT trying to import e-sparqlEndpoint (root DPU template), but rather its child (e-sparqlEndpoint 1). So this could fail with such message only if the same named child of e-sparqlEndpoint already exists in the system.

Expected behavior: Child DPU template may be imported.

Problem is probably with: https://github.com/UnifiedViews/Core/blob/develop/commons-app/src/main/java/cz/cuni/mff/xrg/odcs/commons/app/module/DPUModuleManipulator.java#L181-L183 or somewhere around in this method.

Related to #356
Could be related to: #173

@tomas-knap
Copy link
Author

Tested, this works correctly. Will be closed when #521 is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants