Axis2 WSDL- Code Generation and other concerns

1. Axis2 WSDL- Code Generation and other concerns

2. Contents • Scope, Goals and Wish list. • Proposed Architecture • Wooden !!!

3. Code-generation • Scope: • Client stub and server skeleton generation to support invocation of service and to engage add on services (RM, security, etc) • The Data binding is left out in this discussion. • Design Goals. • Generate artifacts that will engage add on service, if specified . • Leave room for client side extensibility based on policy. • Provide for programming language extensibility. • Wish List. • Make the WSDL (with Extensions) to be the principal source of input to the code generation tool.

4. Code generation tool

5. Input Configuration files. • Promote the use of WSDL extensions and policy to build the Input configuration (while providing for other inputs as well). • Configuration Builder will build to the Configuration from different descriptors.

6. Client Side/Server side Code Generation • Required runtime configuration will be generated as deployment descriptors (service.xml, client.xml) • Emitters will be used which are • Program language dependent • Each Emitter is aware of the add on service implementations available.

7. Add on services • Add on services will be incorporated in the form of the form of Modules and handlers and be burnt into the wsdd file. • A add on service implementation modules be made available in aar-drop directory.

8. Deployment Interaction

9. Other Aspects • Sync Async behavior will be burnt into the stub in the client side and server side will be based on a particular Receiver. • MEP Considerations will be handled by the deployment based on the wsdl • Add on services (WS-*) will be burnt into the deployment descriptors. • Deployment will load the proper configurations.

10. Wooden concerns • Eventually Wooden will replace WOM? • Are we to wait for Wooden’s StAX based parsing?

11. Comments ??????