You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Holodeck B2B Pull Request trigger extension
2
2
This extension allows the _Consumer_ application to control when _Pull Request_s are send by Holodeck B2B
3
-
instead of the default fixed intervals. It also allows to specify the _criteria_of a "selective" Pull Request
4
-
as specified in [section 5.1 of ebMS V3 part 2 (Advanced Features)](http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/ebms-v3.0-part2-cs01.html#__RefHeading__435723_822242408).
3
+
instead of the default fixed intervals. It also allows to specify the _simple selection criteria_of a "selective"
4
+
Pull Request as specified in [section 5.1 of ebMS V3 part 2 (Advanced Features)](http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/ebms-v3.0-part2-cs01.html#__RefHeading__435723_822242408).
5
5
6
6
Currently the trigger mechanism is file based; the back-end application writes a XML document to a specific
7
7
directory where it is read by the extension and a corresponding Pull Request is triggered.
@@ -37,7 +37,7 @@ directory specified in the _watchPath_ parameter of the watcher described above.
37
37
are XML documents that MUST have the "xml" extension. They must contain at least the P-Mode that governs
38
38
the processing of the Pull Request and can further configure the _MessageId_ of the Pull Request, the MPC
39
39
[sub-channel] and selection criteria to use for pulling. Their structure is defined by XML schema
0 commit comments