Skip to content

Fixed typos in README.md #3

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

Open
alterdego wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed typos in README.md #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Out of the box, a best practice is to define a common message flow in its own be
file which may be imported into other message flows. This approach however has some limitations:

* It's input and output channels are referenced in every consuming flow. Each common flow must ensure unique channel names
* True encapsuation is impossible as any internal channels and components are exposed to the consuming flow. Note that these must have
* True encapsulation is impossible as any internal channels and components are exposed to the consuming flow. Note that these must have
unique names as well
* Since a common flow is statically bound to channels, it cannot be used in a chain without implementing some type of service-activator/
gateway wrapper.
Expand Down