| 00000 |
[OASIS Issue Tracker] (EBXMLMSG-108) Unclear if empty ConversationId is allowed |
OASIS Issues Tracker
|
2017-08-03 11:05 |
| 00001 |
[OASIS Issue Tracker] (EBXMLMSG-107) Extensibility of ebMS3 error codes |
OASIS Issues Tracker
|
2017-08-03 11:23 |
| 00002 |
[OASIS Issue Tracker] (EBXMLMSG-101) AS4 5.1.4/5.1.4 which message parts to sign |
OASIS Issues Tracker
|
2017-08-03 11:53 |
| 00003 |
[OASIS Issue Tracker] (EBXMLMSG-108) Unclear if empty ConversationId is allowed |
OASIS Issues Tracker
|
2017-08-03 12:07 |
| 00004 |
[OASIS Issue Tracker] (EBXMLMSG-105) *.Initiator.* and *.Responder.* in PMode |
OASIS Issues Tracker
|
2017-08-03 12:32 |
| 00005 |
[OASIS Issue Tracker] (EBXMLMSG-100) 5.1.8 RefToMessageId in Receipts |
OASIS Issues Tracker
|
2017-08-03 13:59 |
| 00006 |
[OASIS Issue Tracker] (EBXMLMSG-83) Referencing XML documents in SOAP body |
OASIS Issues Tracker
|
2017-08-03 15:14 |
| 00007 |
Position of ebMS3 SOAP Root Part |
Pim van der Eijk
|
2017-08-16 13:16 |
| 00008 |
[OASIS Issue Tracker] (EBXMLMSG-108) Unclear if empty ConversationId is allowed |
OASIS Issues Tracker
|
2017-08-28 11:16 |
| 00009 |
[OASIS Issue Tracker] (EBXMLMSG-108) Unclear if empty ConversationId is allowed |
OASIS Issues Tracker
|
2017-08-28 11:20 |
