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

ServiceTemplate Contains Two Top Nodes with PythonArchiveArtifact and WAR Upload #29

Closed
LaviniaStiliadou opened this issue Oct 23, 2023 · 0 comments · Fixed by PlanQK/workflow-modeler#100

Comments

@LaviniaStiliadou
Copy link

Current Behavior:

When uploading a PythonArchiveArtifact and then a WAR to the service, the resulting ServiceTemplate contains two top nodes. This behavior is inconsistent with the expected behavior, as only one top node should be present in the ServiceTemplate.

Expected Behavior:

The ServiceTemplate should contain a single top node, regardless of whether a PythonArchiveArtifact is uploaded before a WAR or vice versa.

Steps to Reproduce:

  1. Upload a PythonArchiveArtifact to the WF modeler-
  2. Upload a WAR to the WF modeler.

Result:

The resulting ServiceTemplate contains two top nodes, which is not the expected behavior.

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

Successfully merging a pull request may close this issue.

1 participant