There's a fix for this in WSME trunk, but it only works with Pecan at the
moment. Now that I'm back from vacation, I will resume working on getting
WSME onto StackForge and a new release cut.
Doug
On Tue, Aug 6, 2013 at 7:36 PM, Devananda van der Veen
devananda@gmail.com wrote:
On Tue,
On Mon, Aug 5, 2013 at 11:03 AM, Mac Innes, Kiall ki...@hp.com wrote:
While the topic of WSME is open - Has anyone actually tried using it?
snip
I would be very cautious about assuming WSME can support anything we
need when the absolute fundamentals of building a REST API are totally MIA.
On Tue, Aug 6, 2013 at 5:35 AM, Mac Innes, Kiall ki...@hp.com wrote:
So,
From experimenting with, and looking at the WSME code - raising a
status with `pecan.abort(404)` etc doesn't actually work.
WSME sees that, and helpfully swaps it out for a HTTP 500 ;)
The author of WSME even says
James Slagle james.sla...@gmail.com wrote:
WSME + pecan is being used in Tuskar:
https://github.com/tuskar/tuskar (OpenStack management API)
We encountered the same issue discussed here. A solution we settled
on for now was to use a custom Renderer class that could handle
different
On 06/08/13 21:56, Jonathan LaCour wrote:
James Slagle james.sla...@gmail.com wrote:
WSME + pecan is being used in Tuskar:
https://github.com/tuskar/tuskar (OpenStack management API)
We encountered the same issue discussed here. A solution we settled
on for now was to use a custom Renderer
On Tue, Aug 6, 2013 at 2:17 PM, Mac Innes, Kiall ki...@hp.com wrote:
On 06/08/13 21:56, Jonathan LaCour wrote:
James Slagle james.sla...@gmail.com wrote:
WSME + pecan is being used in Tuskar:
https://github.com/tuskar/tuskar (OpenStack management API)
We encountered the same issue
On 05/08/13 16:09, John Garbutt wrote:
On 5 August 2013 15:15, Anne Gentleannegen...@justwriteclick.com wrote:
On Mon, Aug 5, 2013 at 8:55 AM, John Garbuttj...@johngarbutt.com wrote:
Given we seem to be leaning towards WSME:
