The dashboard summarizes the results of unit and interop testing of the Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment specifications, in fulfillment of the CR exit criteria (Framework and Attachment). Interop scenarios and test files are on the W3C CVS archive. Check out the high level summary and features & test coverage description.
Testing is based on implementations (in alphabetical order) from:
Organization | Reporter | Round-1 | Round-2-WSDL11 | Round-2-WSDL20 | Round-3-WSDL11 | Round-3-WSDL20 | Round-4-Media-Type | Round-4-External-Policy-Attachment-WSDL11 | Round-4-External-Policy-Attachment-WSDL20 | Round-4-UDDI-Attachment-Interop | Round-4-UDDI-Attachment-Unittest | Round-4-Negative-Test |
Axway | Iustin IRIMIA |
|||||||||||
BEA | Symon Chang |
|||||||||||
HP | ||||||||||||
IBM | Doug Davis |
|||||||||||
Layer-7 | Steve Jones |
|||||||||||
Microsoft | Mohammad Makarechian |
|||||||||||
Oracle | Ramana Turlapati |
|||||||||||
Sun | Fabian Ritzmann |
|||||||||||
webMethods | Prasad Yendluri Sathyamoorthy Sridhar |
|||||||||||
WSO2 | Sanka Samaranyake |
|||||||||||
WSO2-C | Sanka Samaranyake |
Round 1 test cases are WS-Policy unit test cases for testing policy normalize, merge and intersect operations. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | Axway | BEA | IBM | Layer-7 | Microsoft | Sun | WSO2 |
R1T1 | normalize(Policy1.xml) | |||||||
R1T2 | normalize(Policy2.xml) | |||||||
R1T3 | normalize(Policy3.xml) | |||||||
R1T4 | normalize(Policy4.xml) | |||||||
R1T5 | normalize(Policy5.xml) | |||||||
R1T6 | normalize(Policy6.xml) | |||||||
R1T7 | normalize(Policy7.xml) | |||||||
R1T8 | normalize(Policy8.xml) | |||||||
R1T9 | normalize(Policy9.xml) | |||||||
R1T10 | normalize(Policy10.xml) | |||||||
R1T11 | normalize(Policy11.xml) | |||||||
R1T12 | normalize(Policy12.xml) | |||||||
R1T13 | normalize(Policy13.xml) | |||||||
R1T14 | normalize(Policy14.xml) | |||||||
R1T15 | normalize(Policy15.xml) | |||||||
R1T16 | normalize(Policy16.xml) | |||||||
R1T17 | normalize(Policy17.xml) | |||||||
R1T18 | normalize(Policy18.xml) | |||||||
R1T19 | normalize(Policy19.xml) | |||||||
R1T20 | normalize(Policy20.xml) | |||||||
R1T27 | normalize(Policy27.xml) | |||||||
R1T28 | normalize(Policy28.xml) | |||||||
R1T29 | merge(Policy21.xml, Policy21.xml) | |||||||
R1T30 | merge(Policy21.xml, Policy22.xml) | |||||||
R1T31 | merge(Policy21.xml, Policy23.xml) | |||||||
R1T32 | merge(Policy21.xml, Policy24.xml) | |||||||
R1T33 | merge(Policy21.xml, Policy25.xml) | |||||||
R1T34 | merge(Policy22.xml, Policy21.xml) | |||||||
R1T35 | merge(Policy22.xml, Policy22.xml) | |||||||
R1T36 | merge(Policy22.xml, Policy23.xml) | |||||||
R1T37 | merge(Policy22.xml, Policy24.xml) | |||||||
R1T38 | merge(Policy22.xml, Policy25.xml) | |||||||
R1T39 | merge(Policy23.xml, Policy21.xml) | |||||||
R1T40 | merge(Policy23.xml, Policy22.xml) | |||||||
R1T41 | merge(Policy23.xml, Policy23.xml) | |||||||
R1T42 | merge(Policy23.xml, Policy24.xml) | |||||||
R1T43 | merge(Policy23.xml, Policy25.xml) | |||||||
R1T44 | merge(Policy24.xml, Policy21.xml) | |||||||
R1T45 | merge(Policy24.xml, Policy22.xml) | |||||||
R1T46 | merge(Policy24.xml, Policy23.xml) | |||||||
R1T47 | merge(Policy24.xml, Policy24.xml) | |||||||
R1T48 | merge(Policy24.xml, Policy25.xml) | |||||||
R1T49 | merge(Policy25.xml, Policy21.xml) | |||||||
R1T50 | merge(Policy25.xml, Policy22.xml) | |||||||
R1T51 | merge(Policy25.xml, Policy23.xml) | |||||||
R1T52 | merge(Policy25.xml, Policy24.xml) | |||||||
R1T53 | merge(Policy25.xml, Policy25.xml) | |||||||
R1T54 | intersect(Policy21.xml, Policy21.xml) | |||||||
R1T55 | intersect(Policy21.xml, Policy22.xml) | |||||||
R1T56 | intersect(Policy21.xml, Policy23.xml) | |||||||
R1T57 | intersect(Policy21.xml, Policy24.xml) | |||||||
R1T58 | intersect(Policy21.xml, Policy25.xml) | |||||||
R1T59 | intersect(Policy21.xml, Policy26.xml) | |||||||
R1T60 | intersect(Policy21.xml, Policy27.xml) | |||||||
R1T61 | intersect(Policy22.xml, Policy21.xml) | |||||||
R1T62 | intersect(Policy22.xml, Policy22.xml) | |||||||
R1T63 | intersect(Policy22.xml, Policy23.xml) | |||||||
R1T64 | intersect(Policy22.xml, Policy24.xml) | |||||||
R1T65 | intersect(Policy22.xml, Policy25.xml) | |||||||
R1T66 | intersect(Policy22.xml, Policy26.xml) | |||||||
R1T67 | intersect(Policy22.xml, Policy27.xml) | |||||||
R1T68 | intersect(Policy23.xml, Policy21.xml) | |||||||
R1T69 | intersect(Policy23.xml, Policy22.xml) | |||||||
R1T70 | intersect(Policy23.xml, Policy23.xml) | |||||||
R1T71 | intersect(Policy23.xml, Policy24.xml) | |||||||
R1T72 | intersect(Policy23.xml, Policy25.xml) | |||||||
R1T73 | intersect(lax, Policy23.xml, Policy26.xml) | |||||||
R1T74 | intersect(Policy23.xml, Policy26.xml) | |||||||
R1T75 | intersect(Policy23.xml, Policy27.xml) | |||||||
R1T76 | intersect(Policy24.xml, Policy21.xml) | |||||||
R1T77 | intersect(Policy24.xml, Policy22.xml) | |||||||
R1T78 | intersect(Policy24.xml, Policy23.xml) | |||||||
R1T79 | intersect(Policy24.xml, Policy24.xml) | |||||||
R1T80 | intersect(Policy24.xml, Policy25.xml) | |||||||
R1T81 | intersect(lax, Policy24.xml, Policy26.xml) | |||||||
R1T82 | intersect(Policy24.xml, Policy26.xml) | |||||||
R1T83 | intersect(Policy24.xml, Policy27.xml) | |||||||
R1T84 | intersect(Policy25.xml, Policy21.xml) | |||||||
R1T85 | intersect(Policy25.xml, Policy22.xml) | |||||||
R1T86 | intersect(Policy25.xml, Policy23.xml) | |||||||
R1T87 | intersect(Policy25.xml, Policy24.xml) | |||||||
R1T88 | intersect(Policy25.xml, Policy25.xml) | |||||||
R1T89 | intersect(lax, Policy25.xml, Policy26.xml) | |||||||
R1T90 | intersect(Policy25.xml, Policy26.xml) | |||||||
R1T91 | intersect(Policy25.xml, Policy27.xml) | |||||||
R1T92 | intersect(Policy26.xml, Policy21.xml) | |||||||
R1T93 | intersect(Policy26.xml, Policy22.xml) | |||||||
R1T94 | intersect(lax, Policy26.xml, Policy23.xml) | |||||||
R1T95 | intersect(Policy26.xml, Policy23.xml) | |||||||
R1T96 | intersect(lax, Policy26.xml, Policy24.xml) | |||||||
R1T97 | intersect(Policy26.xml, Policy24.xml) | |||||||
R1T98 | intersect(lax, Policy26.xml, Policy25.xml) | |||||||
R1T99 | intersect(Policy26.xml, Policy25.xml) | |||||||
R1T100 | intersect(Policy26.xml, Policy26.xml) | |||||||
R1T101 | intersect(Policy26.xml, Policy27.xml) | |||||||
R1T102 | intersect(Policy27.xml, Policy21.xml) | |||||||
R1T103 | intersect(Policy27.xml, Policy22.xml) | |||||||
R1T104 | intersect(Policy27.xml, Policy23.xml) | |||||||
R1T105 | intersect(Policy27.xml, Policy24.xml) | |||||||
R1T106 | intersect(Policy27.xml, Policy25.xml) | |||||||
R1T107 | intersect(Policy27.xml, Policy26.xml) | |||||||
R1T108 | intersect(Policy27.xml, Policy27.xml) |
Round 2 WSDL 11 test cases are WS-Policy unit test cases for testing effective policy computation for policies attached to WSDL 11 policy subjects. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | Axway | BEA | IBM | Layer-7 | Microsoft | Sun | WSO2 |
R2WSDL11T1 | effective policy (Policy Subject=Service, Service=QName) | |||||||
R2WSDL11T2 | effective policy (Policy Subject=Endpoint, Service=QName, Port=QName) | |||||||
R2WSDL11T3 | effective policy (Policy Subject=Operation, Service=QName, Port=QName, Operation=QName) | |||||||
R2WSDL11T4 | effective policy (Policy Subject=Input Message, Service=QName, Port=QName, Operation=QName) | |||||||
R2WSDL11T5 | effective policy (Policy Subject=Output Message, Service=QName, Port=QName, Operation=QName) | |||||||
R2WSDL11T6 | effective policy (Policy Subject=Fault Message, Service=QName, Port=QName, Operation=QName) | |||||||
R2WSDL11T7 | effective policy (Policy Subject=Service, Service=QName, xml:id) | |||||||
R2WSDL11T8 | effective policy (Policy Subject=Endpoint, Service=QName, Port=QName, xml:id) | |||||||
R2WSDL11T9 | effective policy (Policy Subject=Operation, Service=QName, Port=QName, Operation=QName, xml:id) | |||||||
R2WSDL11T10 | effective policy (Policy Subject=Input Message, Service=QName, Port=QName, Operation=QName, xml:id) | |||||||
R2WSDL11T11 | effective policy (Policy Subject=Output Message, Service=QName, Port=QName, Operation=QName, xml:id) | |||||||
R2WSDL11T12 | effective policy (Policy Subject=Fault Message, Service=QName, Port=QName, Operation=QName, xml:id) |
Round 2 WSDL 20 test cases are WS-Policy unit test cases for testing effective policy computation for policies attached to WSDL 20 policy subjects. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | IBM | WSO2-JAVA | WSO2-C |
R2WSDL20T1 | effective policy (Service-1) | |||
R2WSDL20T2 | effective policy (Service-2) | |||
R2WSDL20T3 | effective policy (Service-1, Endpoint-1A) | |||
R2WSDL20T4 | effective policy (Service-1, Endpoint-1B) | |||
R2WSDL20T5 | effective policy (Service-2, Endpoint-2A) | |||
R2WSDL20T6 | effective policy (Service-2, Endpoint-2B) | |||
R2WSDL20T7 | effective policy (Service-1, Endpoint-1A, Operation-1A) | |||
R2WSDL20T8 | effective policy (Service-1, Endpoint-1B, Operation-1A) | |||
R2WSDL20T9 | effective policy (Service-1, Endpoint-1A, Operation-1B) | |||
R2WSDL20T10 | effective policy (Service-1, Endpoint-1B, Operation-1B) | |||
R2WSDL20T11 | effective policy (Service-2, Endpoint-2A, Operation-2A) | |||
R2WSDL20T12 | effective policy (Service-2, Endpoint-2B, Operation-2A) | |||
R2WSDL20T13 | effective policy (Service-2, Endpoint-2A, Operation-2B) | |||
R2WSDL20T14 | effective policy (Service-2, Endpoint-2B, Operation-2B) | |||
R2WSDL20T15 | effective policy (Service-1, Endpoint-1A, Operation-1A, input) | |||
R2WSDL20T16 | effective policy (Service-1, Endpoint-1B, Operation-1A, input) | |||
R2WSDL20T17 | effective policy (Service-1, Endpoint-1A, Operation-1B, input) | |||
R2WSDL20T18 | effective policy (Service-1, Endpoint-1B, Operation-1B, input) | |||
R2WSDL20T19 | effective policy (Service-2, Endpoint-2A, Operation-2A, input) | |||
R2WSDL20T20 | effective policy (Service-2, Endpoint-2B, Operation-2A, input) | |||
R2WSDL20T21 | effective policy (Service-2, Endpoint-2A, Operation-2B, input) | |||
R2WSDL20T22 | effective policy (Service-2, Endpoint-2B, Operation-2B, input) | |||
R2WSDL20T23 | effective policy (Service-1, Endpoint-1A, Operation-1A, output) | |||
R2WSDL20T24 | effective policy (Service-1, Endpoint-1B, Operation-1A, output) | |||
R2WSDL20T25 | effective policy (Service-1, Endpoint-1A, Operation-1B, output) | |||
R2WSDL20T26 | effective policy (Service-1, Endpoint-1B, Operation-1B, output) | |||
R2WSDL20T27 | effective policy (Service-2, Endpoint-2A, Operation-2A, output) | |||
R2WSDL20T28 | effective policy (Service-2, Endpoint-2B, Operation-2A, output) | |||
R2WSDL20T29 | effective policy (Service-2, Endpoint-2A, Operation-2B, output) | |||
R2WSDL20T30 | effective policy (Service-2, Endpoint-2B, Operation-2B, output) | |||
R2WSDL20T31 | effective policy (Service-1, Endpoint-1A, Operation-1A, outfault) | |||
R2WSDL20T32 | effective policy (Service-1, Endpoint-1B, Operation-1A, outfault) | |||
R2WSDL20T33 | effective policy (Service-1, Endpoint-1A, Operation-1B, outfault) | |||
R2WSDL20T34 | effective policy (Service-1, Endpoint-1B, Operation-1B, outfault) | |||
R2WSDL20T35 | effective policy (Service-2, Endpoint-2A, Operation-2A, outfault) | |||
R2WSDL20T36 | effective policy (Service-2, Endpoint-2B, Operation-2A, outfault) | |||
R2WSDL20T37 | effective policy (Service-2, Endpoint-2A, Operation-2B, outfault) | |||
R2WSDL20T38 | effective policy (Service-2, Endpoint-2B, Operation-2B, outfault) | |||
R2WSDL20T39 | effective policy (Service-1, xml:id) | |||
R2WSDL20T40 | effective policy (Service-2, xml:id) | |||
R2WSDL20T41 | effective policy (Service-1, Endpoint-1A, xml:id) | |||
R2WSDL20T42 | effective policy (Service-1, Endpoint-1B, xml:id) | |||
R2WSDL20T43 | effective policy (Service-2, Endpoint-2A, xml:id) | |||
R2WSDL20T44 | effective policy (Service-2, Endpoint-2B, xml:id) | |||
R2WSDL20T45 | effective policy (Service-1, Endpoint-1A, Operation-1A, xml:id) | |||
R2WSDL20T46 | effective policy (Service-1, Endpoint-1B, Operation-1A, xml:id) | |||
R2WSDL20T47 | effective policy (Service-1, Endpoint-1A, Operation-1B, xml:id) | |||
R2WSDL20T48 | effective policy (Service-1, Endpoint-1B, Operation-1B, xml:id) | |||
R2WSDL20T49 | effective policy (Service-2, Endpoint-2A, Operation-2A, xml:id) | |||
R2WSDL20T50 | effective policy (Service-2, Endpoint-2B, Operation-2A, xml:id) | |||
R2WSDL20T51 | effective policy (Service-2, Endpoint-2A, Operation-2B, xml:id) | |||
R2WSDL20T52 | effective policy (Service-2, Endpoint-2B, Operation-2B, xml:id) | |||
R2WSDL20T53 | effective policy (Service-1, Endpoint-1A, Operation-1A, input, xml:id) | |||
R2WSDL20T54 | effective policy (Service-1, Endpoint-1B, Operation-1A, input, xml:id) | |||
R2WSDL20T55 | effective policy (Service-1, Endpoint-1A, Operation-1B, input, xml:id) | |||
R2WSDL20T56 | effective policy (Service-1, Endpoint-1B, Operation-1B, input, xml:id) | |||
R2WSDL20T57 | effective policy (Service-2, Endpoint-2A, Operation-2A, input, xml:id) | |||
R2WSDL20T58 | effective policy (Service-2, Endpoint-2B, Operation-2A, input, xml:id) | |||
R2WSDL20T59 | effective policy (Service-2, Endpoint-2A, Operation-2B, input, xml:id) | |||
R2WSDL20T60 | effective policy (Service-2, Endpoint-2B, Operation-2B, input, xml:id) | |||
R2WSDL20T61 | effective policy (Service-1, Endpoint-1A, Operation-1A, output, xml:id) | |||
R2WSDL20T62 | effective policy (Service-1, Endpoint-1B, Operation-1A, output, xml:id) | |||
R2WSDL20T63 | effective policy (Service-1, Endpoint-1A, Operation-1B, output, xml:id) | |||
R2WSDL20T64 | effective policy (Service-1, Endpoint-1B, Operation-1B, output, xml:id) | |||
R2WSDL20T65 | effective policy (Service-2, Endpoint-2A, Operation-2A, output, xml:id) | |||
R2WSDL20T66 | effective policy (Service-2, Endpoint-2B, Operation-2A, output, xml:id) | |||
R2WSDL20T67 | effective policy (Service-2, Endpoint-2A, Operation-2B, output, xml:id) | |||
R2WSDL20T68 | effective policy (Service-2, Endpoint-2B, Operation-2B, output, xml:id) | |||
R2WSDL20T69 | effective policy (Service-1, Endpoint-1A, Operation-1A, outfault, xml:id) | |||
R2WSDL20T70 | effective policy (Service-1, Endpoint-1B, Operation-1A, outfault, xml:id) | |||
R2WSDL20T71 | effective policy (Service-1, Endpoint-1A, Operation-1B, outfault, xml:id) | |||
R2WSDL20T72 | effective policy (Service-1, Endpoint-1B, Operation-1B, outfault, xml:id) | |||
R2WSDL20T73 | effective policy (Service-2, Endpoint-2A, Operation-2A, outfault, xml:id) | |||
R2WSDL20T74 | effective policy (Service-2, Endpoint-2B, Operation-2A, outfault, xml:id) | |||
R2WSDL20T75 | effective policy (Service-2, Endpoint-2A, Operation-2B, outfault, xml:id) | |||
R2WSDL20T76 | effective policy (Service-2, Endpoint-2B, Operation-2B, outfault, xml:id) |
WS-Policy Round 3 interop tests use security policy assertions. These tests exercise substantial parts of the Framework and Attaching Policies Using WSDL 1.1.
The following tables enumerate results from implementers based on running these interop tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Requestor/Provider | Axway | BEA | IBM | Layer-7 | Microsoft | Oracle | Sun | WSO2 |
Axway | ||||||||
BEA | ||||||||
IBM | ||||||||
Layer-7 | ||||||||
Microsoft | ||||||||
Oracle | ||||||||
Sun | ||||||||
WSO2 |
Requestor/Provider | Axway | BEA | IBM | Layer-7 | Microsoft | Oracle | Sun | WSO2 |
Axway | ||||||||
BEA | ||||||||
IBM | ||||||||
Layer-7 | ||||||||
Microsoft | ||||||||
Oracle | ||||||||
Sun | ||||||||
WSO2 |
Requestor/Provider | Axway | BEA | IBM | Layer-7 | Microsoft | Oracle | Sun | WSO2 |
Axway | ||||||||
BEA | ||||||||
IBM | ||||||||
Layer-7 | ||||||||
Microsoft | ||||||||
Oracle | ||||||||
Sun | ||||||||
WSO2 |
Requestor/Provider | Axway | BEA | IBM | Layer-7 | Microsoft | Oracle | Sun | WSO2 |
Axway | ||||||||
BEA | ||||||||
IBM | ||||||||
Layer-7 | ||||||||
Microsoft | ||||||||
Oracle | ||||||||
Sun | ||||||||
WSO2 |
WS-Policy Round 3 interop tests use security policy assertions. These tests exercise substantial parts of the Framework and WS-Policy Attachment for WSDL 2.0.
The following tables enumerate results from implementers based on running these interop tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Requestor/Provider | IBM | WSO2 | WSO2-C |
IBM | |||
WSO2 | |||
WSO2-C |
Requestor/Provider | IBM | WSO2 | WSO2-C |
IBM | |||
WSO2 | |||
WSO2-C |
Requestor/Provider | IBM | WSO2 | WSO2-C |
IBM | |||
WSO2 | |||
WSO2-C |
Requestor/Provider | IBM | WSO2 | WSO2-C |
IBM | |||
WSO2 | |||
WSO2-C |
WS-Policy Round 4 Media Type test case test that the new Web Services Policy Media Type is used when a policy document is retrived via HTTP.
IBM | HTTP Endpoint: http://localhost:8080/wspolicy/Policy1.wsp |
Layer-7 | HTTP Endpoint: http://64.180.109.90:10080/ssg/policy/disco?serviceoid=196610&wssp=true |
Microsoft | HTTP Endpoint: http://131.107.153.203/WSPolicyMimeExtTest/Policy1.wsp |
Sun | HTTP Endpoint: http://wsinterop.sun.com:3280/wspolicy_interop/policy.wspolicy |
The following tables enumerate results from implementers based on running these interop tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Requestor/Provider | IBM | Layer-7 | Microsoft | Sun |
IBM | ||||
Layer-7 | ||||
Microsoft | ||||
Sun |
Round 4 External Policy Attachment WSDL11 - these are unit test cases that verify how a consumer processes external policy attachment elements. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | IBM | Oracle |
R4W1-1 | Process external policy attachment elements | ||
R4W1-2 | Process external policy attachment elements |
Round 4 External Policy Attachment WSDL20 - these are unit test cases that verify how a consumer processes external policy attachment elements. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | IBM | WSO2 |
R4W2-1 | Process external policy attachment elements | ||
R4W2-2 | Process external policy attachment elements |
Round 4 UDDI Attachment Interop - these test cases attach and verify policy attachment for UDDI policy subjects.
HP | Inquiry URL: TBD Publish URL: TBD Security URL: TBD |
Layer-7 | Inquiry URL: http://63.119.28.160:2020/registry/uddi/inquiry Publish URL: http://63.119.28.160:2020/registry/uddi/publish Security URL: http://63.119.28.160:2020/registry/uddi/security |
webMethods | Inquiry URL: http://63.119.28.160:2020/registry/uddi/inquiry Publish URL: http://63.119.28.160:2020/registry/uddi/publish Security URL: http://63.119.28.160:2020/registry/uddi/security |
The following tables enumerate results from implementers based on running these interop tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Local Policy Attachment with UDDI v2 - Register a reusable Policy expression as a tModel
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v2 - Attach the reusable Policy to businessEntity
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v2 - Attach the reusable Policy to businessService
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v2 - Attach the reusable Policy to bindingTemplate
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Attach a remote Policy reference to businessEntity (UDDI v2)
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Attach a remote Policy reference to businessService (UDDI v2)
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Attach a remote Policy reference to bindingTemplate (UDDI v2)
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v3 - Register a reusable Policy expression as a tModel
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v3 - Attach the reusable Policy to businessEntity
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v3 - Attach the reusable Policy to businessService
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Local Policy Attachment with UDDI v3 - Attach the reusable Policy to bindingTemplate
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Attach a remote Policy reference to businessEntity (UDDI v3)
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Attach a remote Policy reference to businessService (UDDI v3)
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Attach a remote Policy reference to bindingTemplate (UDDI v3)
Requestor/Provider | HP | Layer-7 | webMethods |
HP | |||
Layer-7 | |||
webMethods |
Round 4 UDDI Attachment Unittests are for testing effective policy computation for policies attached to UDDI policy subjects. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | Layer-7 | webMethods |
U2E1 | Service Provider Policy Subject Effective Policy (UDDI v2) | ||
U2E2 | Service Policy Subject Effective Policy (UDDI v2) | ||
U2E3 | Endpoint Policy Subject Effective Policy (UDDI v2) | ||
U3E1 | Service Provider Policy Subject Effective Policy (UDDI v3) | ||
U3E2 | Service Policy Subject Effective Policy (UDDI v3) | ||
U3E3 | Endpoint Policy Subject Effective Policy (UDDI v3) |
These test cases are invalid policy expressions. The following table enumerates results from implementers based on running these unit tests. Green indicates a successful outcome, red indicates a failure and no color indicates 'no claims'.
Name | Description | BEA | IBM | Layer-7 | Microsoft | Sun |
R4Negative1 | Policy-Negative-1.xml | |||||
R4Negative2 | Policy-Negative-2.xml | |||||
R4Negative3 | Policy-Negative-3.xml |
The following table enumerates features in the Framework and Attachment drafts, identifies features that are covered by the test (s) & any on-going test (s) development (marked in yellow) and highlights features without any test coverage (marked in red).
Serial | Section Number | Feature | Test Case (s) | Notes |
1 | P 4.1 | Policy expression - normal form |
Round-1
Round-3-WSDL11 Round-3-WSDL20 |
|
2 | P 4.1 | Policy expression - normal form with nested policy expression |
Round-1
Round-3-WSDL11 Round-3-WSDL20 |
|
3 | P 4.2 | Policy expression - wsu:Id attribute |
Round-2-WSDL11
Round-2-WSDL20 Round-3-WSDL11 Round-3-WSDL20 |
|
4 | P 4.2 | Policy expression - xml:id attribute |
Round-2-WSDL11
Round-2-WSDL20 |
|
5 | P 4.2 | Policy expression - Name attribute |
Round-2-WSDL11
|
|
6 | P 4.3.1 | Compact form - optional policy assertions |
Round-1
|
|
7 | P 4.3.2 | Compact form - nested policy expression |
Round-1
Round-3-WSDL11 Round-3-WSDL20 |
|
8 | P 4.3.3 | Compact form - policy operator - Policy |
Round-1
Round-2-WSDL11 Round-2-WSDL20 Round-3-WSDL11 Round-3-WSDL20 Round-4-Media-Type Round-4-External-Policy-Attachment-WSDL11 Round-4-External-Policy-Attachment-WSDL20 Round-4-Negative-Test |
|
9 | P 4.3.3 | Compact form - policy operator - All |
Round-1
Round-2-WSDL11 Round-2-WSDL20 Round-3-WSDL11 Round-3-WSDL20 Round-4-Media-Type Round-4-External-Policy-Attachment-WSDL11 Round-4-External-Policy-Attachment-WSDL20 Round-4-Negative-Test |
|
10 | P 4.3.3 | Compact form - policy operator - ExactlyOne |
Round-1
Round-2-WSDL11 Round-2-WSDL20 Round-3-WSDL11 Round-3-WSDL20 Round-4-Media-Type Round-4-External-Policy-Attachment-WSDL11 Round-4-External-Policy-Attachment-WSDL20 Round-4-Negative-Test |
|
11 | P 4.3.4 | Compact form - policy references |
Round-2-WSDL11
Round-2-WSDL20 Round-3-WSDL11 Round-3-WSDL20 Round-4-External-Policy-Attachment-WSDL11 Round-4-External-Policy-Attachment-WSDL20 |
|
12 | P 4.3.5 | Policy inclusion (expression identified by an ID) |
Round-2-WSDL11
Round-2-WSDL20 Round-3-WSDL11 Round-3-WSDL20 |
|
13 | P 4.3.5 | Policy inclusion (external policy expression) |
Round-2-WSDL11
|
|
14 | P 4.3.6 | Normalize |
Round-1
|
|
15 | P 4.4 | Ignorable policy assertions |
Round-1
|
|
16 | P 4.5 | Policy intersection – strict mode |
Round-1
|
|
17 | P 4.5 | Policy intersection – lax mode |
Round-1
|
|
18 | P 4.5 | Policy expression + XML Base |
Round-1
|
|
19 | P Appendix A | application/wspolicy+xml media type |
Round-4-Media-Type
|
|
20 | PA 3.4.1 | External Policy Attachment: URI domain expression + IRI References for WSDL 20 Components |
Round-4-External-Policy-Attachment-WSDL20
|
|
21 | PA 3.4.1 | External Policy Attachment: URI domain expression + WSDL 11 Element Identifiers |
Round-4-External-Policy-Attachment-WSDL11
|
|
22 | PA 4.1.1 | WSDL11: Effective policy of a service policy subject |
Round-2-WSDL11
|
|
23 | PA 4.1.2 | WSDL11: Effective policy of an endpoint policy subject |
Round-2-WSDL11
Round-3-WSDL11 |
|
24 | PA 4.1.3 | WSDL11: Effective policy of an operation policy subject |
Round-2-WSDL11
|
|
25 | PA 4.1.4 | WSDL11: Effective policy of an input message policy subject |
Round-2-WSDL11
Round-3-WSDL11 |
|
26 | PA 4.1.4 | WSDL11: Effective policy of an output message policy subject |
Round-2-WSDL11
Round-3-WSDL11 |
|
27 | PA 4.1.4 | WSDL11: Effective policy of a fault message policy subject |
Round-2-WSDL11
|
|
28 | PA 5.4.1 | WSDL20: Effective policy of a service policy subject |
Round-2-WSDL20
|
|
29 | PA 5.4.2 | WSDL20: Effective policy of an endpoint policy subject |
Round-2-WSDL20
Round-3-WSDL20 |
|
30 | PA 5.4.3 | WSDL20: Effective policy of an operation policy subject |
Round-2-WSDL20
|
|
31 | PA 5.4.4 | WSDL20: Effective policy of an input message policy subject |
Round-2-WSDL20
Round-3-WSDL20 |
|
32 | PA 5.4.5 | WSDL20: Effective policy of an output message policy subject |
Round-2-WSDL20
Round-3-WSDL20 |
|
33 | PA 5.4.6 and PA 5.4.7 | WSDL20: Effective policy of an input/output fault message policy subject |
Round-2-WSDL20
|
|
34 | PA 6.1.1 | UDDI: Effective policy of a service provider policy subject |
Round-4-UDDI-Attachment-Unittest
|
|
35 | PA 6.1.2 | UDDI: Effective policy of a service policy subject |
Round-4-UDDI-Attachment-Unittest
|
|
36 | PA 6.1.3 | UDDI: Effective policy of an endpoint policy subject |
Round-4-UDDI-Attachment-Unittest
|
|
37 | PA 6.2 | UDDI: Referencing remote policy expressions |
Round-4-UDDI-Attachment-Interop
|
|
38 | PA 6.3 | UDDI: Registering reusable policy expressions |
Round-4-UDDI-Attachment-Interop
|
|
39 | PA 6.4 | UDDI: Registering policies in UDDI V3 |
Round-4-UDDI-Attachment-Interop
|
|
40 | Negative Test Cases |
Round-4-Negative-Test
|