FAQ

On Wed, Apr 08, 2009 at 06:00:36PM -0700, Bruce McKenzie wrote:
Note that if you have a custom request class in your application, and it does
not inherit from C<Catalyst::Request::REST>, your application will fail with an
error indicating a conflict the first time it tries to use
C<Catalyst::Request::REST>'s functionality. To fix this error, make sure your
custom request class inherits from C<Catalyst::Request::REST>.
-------
but that doesn't seems like an option here. (These are peers, not parent/child
classes)

Am I missing something obvious?
Doesn't this suck? It should clearly be a request role instead of a request
class.

Seriously, I plan to fix this very soon, and I'm sorry it's still biting you.

hdp.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 3 | next ›
Discussion Overview
groupcatalyst @
categoriescatalyst, perl
postedApr 9, '09 at 1:00a
activeApr 9, '09 at 1:20a
posts3
users3
websitecatalystframework.org
irc#catalyst

People

Translate

site design / logo © 2022 Grokbase