W3C::SOAP tasks still to be done
- Type::Tiny
-
Type::Tiny looks like it would give a more consistant and easier to use type interface than the current mish-mash of Moose and MooseX::Types currently used.
- AnyEvent support
-
Need to rearrange the internals so that a request could be done as part of an event loop. This needs some thinking of how the client is to be broken up and how to determine to use blocking requests and event loop requests.
- Improve XML Schema support
-
Currently I can't pass http://www.w3.org/2001/XMLSchema.xsd due to not supporting unions and lists. Support for arrays probably is also needed. The following schemas should all be abled to be passed with out error
- WSDL's with multiple inputs and outputs
-
The current code only allows for one input and zero or one output. It looks like support for zero or more for each is required.
- WSDL's with specific fault operations
-
Currently defined faults are not handled with object creations only default SOAP faults are handled
- Improve test coverage
-
Need many more tests to make sure everything is working as expected
- Documentation
-
Some very basic documentation is done but much more work is needed.
- Server creation
-
Helpers to create SOAP servers, Catalyst/Dancer/Mojolicious helpers.
- Mock services helper
-
Helper to create mock responses based on requests (dependant on server creation). Should be able to work in two different ways eg a recording operation so that a client sends requests which the mock server proxies to the real server, stores the results against the request and sends back the response. The other method is to look up the request to see if their already is a response and returns that (the true mock operation).
- WS-Security
-
Currently the Username part of the spec has some form of implementation but their doesn't exist a way of auto generating this or other security forms from the WSDL.