1. GT WS Core: Specification Upgrade

2. 2 Current Implementation l WS Addressing: March 2004 version l WSRF: June 2004 working draft l WSN: June 2004 working draft l SOAP 1.1 l Apache Axis u Trunk: 1.5 with patches u 4.0.x : 1.2 with patches

3. 3 Specification Upgrade l Specifications: u WSRF 1.2 u WSN 1.3 u WS Addressing 1.0 l Implications u No loss of functionality u Some optional additional functionality u Wire incompatible with older version u Some OGF profiles use the final version u Interoperate with other implementations

4. 4 Support final specifications only l In place replacement l Replace u Operation providers u Core API u Handlers that parse WS Addressing headers

5. 5 Implications l New clients cannot interoperate with old servers and vice versa. l EPRs will be different l Service developer will need to update all WSDLs to use new specifications l Minor core API change u EPR creation and processing u Notification processing

6. 6 Support both sets of specification l Container can host services that use either draft or final specifications l Treat each set of specification as operational universe l New set of operation providers and core API for final draft processing l Additional handler to parse WS Addressing final version

7. 7 Implications l Existing client/server interaction will not change l Services that need to exist in multiple universe need u Multiple WSDLs and deployment descriptors u Can share application logic l Service developer must choose appropriate u WSDL u Operation provider u Core API for specification dependent code

8. 8 Questions l Do you need final versions of WSRF/WSN for your project l Do you interoperate with other WSRF/WSN implementations l Do you need to host services with draft and final versions of the specification in same container