gt ws core: specification upgrade. 2 current implementation l ws addressing: march 2004 version l...
TRANSCRIPT
GT WS Core: Specification Upgrade
2
Current Implementation
WS Addressing: March 2004 version WSRF: June 2004 working draft WSN: June 2004 working draft SOAP 1.1 Apache Axis
Trunk: 1.5 with patches 4.0.x : 1.2 with patches
3
Specification Upgrade
Specifications: WSRF 1.2 WSN 1.3 WS Addressing 1.0
Implications No loss of functionality Some optional additional functionality Wire incompatible with older version Some OGF profiles use the final version Interoperate with other implementations
4
Support final specifications only
In place replacement Replace
Operation providers Core API Handlers that parse WS Addressing headers
5
Implications
New clients cannot interoperate with old servers and vice versa.
EPRs will be different Service developer will need to update all
WSDLs to use new specifications Minor core API change
EPR creation and processing Notification processing
6
Support both sets of specification
Container can host services that use either draft or final specifications
Treat each set of specification as operational universe
New set of operation providers and core API for final draft processing
Additional handler to parse WS Addressing final version
7
Implications
Existing client/server interaction will not change
Services that need to exist in multiple universe need Multiple WSDLs and deployment descriptors Can share application logic
Service developer must choose appropriate WSDL Operation provider Core API for specification dependent code
8
Questions
Do you need final versions of WSRF/WSN for your project
Do you interoperate with other WSRF/WSN implementations
Do you need to host services with draft and final versions of the specification in same container