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

Clarification needed on p:choose #662

Closed
eriksiegel opened this Issue Dec 4, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@eriksiegel
Contributor

eriksiegel commented Dec 4, 2018

While reviewing what I wrote about p:choose I stumbled upon this statement:

In order to maintain consistency with respect to the default readable port, if any subpipeline has a primary output port, even implicitly, then every subpipline must have exactly the same primary output port. In some cases, this may require making the implicit primary output explicit in order to assure that it has the same name.

What is exactly meant with exactly the same? Same name, ok. But same sequence type, same content-types also?

@xml-project

This comment has been minimized.

Contributor

xml-project commented Dec 4, 2018

Yes, you are right. "Exactly" means only the name. In the next but one paragraph it is said that @sequence and @content-types do not need to be the same.
We probably should simply avoid the word "exactly".

@ndw ndw self-assigned this Dec 4, 2018

@ndw

This comment has been minimized.

Contributor

ndw commented Dec 4, 2018

Good catch. The same is true of try/catch.

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