
Originally, if WSME received an Accept or Content-Type header that was not aligned with what it was prepared to handle it would error out with a 500 status code. This is not good behavior for a web service. In the process of trying to fix this it was discovered that the content-negotiation code within WSME (the code that, in part, looks for a suitable protocol handler for a request) and tests of that code are incorrect, violating expected HTTP behaviors. GET requests are passing Content-Type headers to declare the desired type of representation in the response. This is what Accept is for. Unfortunately the server-side code was perfectly willing to accept this behavior. These changes correct that. Closes-Bug: 1419110 Change-Id: I2b5c0075611490c047b27b1b43b0505fc5534b3b
Web Services Made Easy
Introduction
Web Services Made Easy (WSME) simplifies the writing of REST web services by providing simple yet powerful typing, removing the need to directly manipulate the request and the response objects.
WSME can work standalone or on top of your favorite Python web (micro)framework, so you can use both your preferred way of routing your REST requests and most of the features of WSME that rely on the typing system like:
- Alternate protocols, including those supporting batch-calls
- Easy documentation through a Sphinx extension
WSME is originally a rewrite of TGWebServices with a focus on extensibility, framework-independance and better type handling.
How Easy ?
Here is a standalone wsgi example:
from wsme import WSRoot, expose
class MyService(WSRoot):
@expose(unicode, unicode) # First parameter is the return type,
# then the function argument types
def hello(self, who=u'World'):
return u"Hello {0} !".format(who)
ws = MyService(protocols=['restjson', 'restxml', 'soap'])
application = ws.wsgiapp()
With this published at the /ws
path of your application,
you can access your hello function in various protocols:
URL | Returns |
---|---|
http://<server>/ws/hello.json?who=you |
"Hello you !" |
http://<server>/ws/hello.xml |
<result>Hello World !</result> |
http://<server>/ws/api.wsdl |
A WSDL description for any SOAP client. |
Main features
- Very simple API.
- Supports user-defined simple and complex types.
- Multi-protocol : REST+Json, REST+XML, SOAP, ExtDirect and more to come.
- Extensible : easy to add more protocols or more base types.
- Framework independence : adapters are provided to easily integrate your API in any web framework, for example a wsgi container, Pecan, TurboGears, Flask, cornice...
- Very few runtime dependencies: webob, simplegeneric. Optionnaly lxml and simplejson if you need better performances.
- Integration in Sphinx for
making clean documentation with
wsmeext.sphinxext
.
Install
pip install WSME
or, if you do not have pip on your system or virtualenv
easy_install WSME
Changes
- Read the Changelog
Getting Help
- Read the WSME Documentation.
- Questions about WSME should go to the python-wsme mailinglist.
Contribute
- Report issues
- Source code
-
git clone https://github.com/stackforge/wsme/
- Gerrit
-
https://review.openstack.org/#/q/project:stackforge/wsme,n,z/