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

IntermediateCatchEvent/TimerEventDefinition support #45

Open
SirWaddles opened this issue May 23, 2018 · 0 comments
Open

IntermediateCatchEvent/TimerEventDefinition support #45

SirWaddles opened this issue May 23, 2018 · 0 comments

Comments

@SirWaddles
Copy link
Contributor

I've built support for the intermediateCatchEvent with a timerEventDefinition (although this won't quite work fully in the bundle as the delay/timers are handled separately in my instance)

At the moment, this just adds the specification, interfaces and such. I don't really understand the interim format between the Bpmn2Reader and the WorkflowBuilder. On my branch, the WorkflowBuilder creates a TimerEventDefinition and the Bpmn2Reader is expected to pass it back. This doesn't seem like it would match the style of the bundle, or fit with what I think is format-agnostic building.

The main problem is that, there is number of different types of EventDefinitions that could be submitted alongside the CatchEvent, so I'm not sure what the format would look like without using a very large switch/case or something.

I don't mind rebuilding my branch so that it only includes the new elements (mine has some other pretty significant changes as well that I don't think would work upstream.)

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

No branches or pull requests

1 participant