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.

Sign up for GitHub

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

Jump to bottom

BPMN Parsing should ignore third-party namespaces #9438

Closed
berndruecker opened this issue May 23, 2022 · 2 comments
Closed

BPMN Parsing should ignore third-party namespaces #9438

berndruecker opened this issue May 23, 2022 · 2 comments
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior

Comments

@berndruecker
Copy link
Member

Is your feature request related to a problem? Please describe.

Some other BPMN tools (e.g. Signavio) add extension attributes to a BPMN model, which should be kept (e.g. for roundtrips or the like). This is a valid use case with BPMN.

Zeebe throws an exception when it sees attributes it does not understand.

Describe the solution you'd like

Zeebe should ignore those attributes (like C7 did if I am not completely mistaken).

Additional context

https://forum.camunda.io/t/could-zeebe-ignore-extension-tags-from-other-vendors/37752
@berndruecker berndruecker added the kind/feature Categorizes an issue or PR as a feature, i.e. new behavior label May 23, 2022
@saig0 saig0 mentioned this issue May 23, 2022
Closed
@saig0
Copy link
Member

saig0 commented May 23, 2022 •
edited
Loading

This issue is related to #4817 and #9424.

@berndruecker berndruecker mentioned this issue Jun 15, 2022
Closed
@menski
Copy link
Contributor

menski commented Jul 22, 2022

Closing as duplicate of #4817

@menski menski closed this as completed Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@menski @berndruecker @Zelldon @saig0