Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Visualization of a message starting multiple Sagas in the Flow Diagram #230
For now, switching between Sagas will be through the message links in Message Flow, and later through Sequence Diagram as well.
Not sure I understand what you mean.
You are raising a good point of whether / how we allow searching for and navigating between Sagas.
I added Saga Status (the little completed/update icon in the flow) as a header in Service Control, but ATM it's working as if there was only one saga. It worked for what I needed to do, but it should allow for multiple sagas.
On the navigation part, I find it inconsistent to switch to the Saga tab (manually, clicking the tab) and not know in which of the related sagas you are. That's why I think we need some sort of "this is the saga name, these are the available sagas" thing. Probably as a drop down next to Toggle Endpoint, but I'd like @sergioc to chime in on that.
referenced this issue
Feb 6, 2014
The drop down option is an interesting one, but there's also the link back to the message at the top of the Saga View.
I think we should experiment a bit with the UI and see how it feels with multiple Sagas per message, and then decide.
Please raise a bug in SC on this limitation. Lets discuss with @johnsimons and team.
some clarifications below:
A message can have multiple Sagas associated with it (i.e. invoked during the message's processing)
After the latest change/pull in SC, implementing this in SI (except for the Saga tab, meaning items 1 and 3 in my initial description) is fairly trivial and should take a few minutes. Please @udidahan and @dannycohen confirm if you want to delay anyway for other reasons. Timing should not be a concern right now. We can implement the saga tab for multiple instances (item 2) later on.
Yes we could do that, but currently the message flow diagram has no dependency of the plugin, so that would be a change
Yes agree, but still highlights the issue
Now I get it, you're talking about the SagaId, SagaType headers.
Setup a call when you're back fro YOW so we can hash it out. Think we need
On Mon, May 25, 2015 at 12:52 AM, John Simons firstname.lastname@example.org