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?
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?
class.
Seriously, I plan to fix this very soon, and I'm sorry it's still biting you.
hdp.
