Fotango Ltd > Froody-42.034 > Froody::Error::Standard

Download:
Froody-42.034.tar.gz

Annotate this POD

CPAN RT

Open  0
View/Report Bugs
Source   Latest Release: Froody-42.041_2

NAME ^

Froody::Error::Standard - Documentation describing the standard errors

DESCRIPTION ^

This page describes the standard errors that you can get with Froody

froody

Errors coming from withing the Froody system, normally because someone hasn't declared everything right for a method, or there's a missing method or something like that

froody.convert

Problem involving converting one Froody::Response to another.

froody.convert.nomethod

There's no method defined for this response, and we need it to do the conversion of one response to another.

froody.convert.nostructure

There's no response specification for the method that this response uses and we need it to do the conversion from one type of response to the other.

froody.invoke

Problem invoking a method

froody.invoke.badresponse

We dispatched the method okay, and everything's fine, apart from the fact that we didn't get a valid Froody::Response back. Ooops.

froody.invoke.noinvoker

There isn't an invoker defined for this method, and you tryed to invoke it.

froody.invoke.nomethod

No method name was passed to the dispatcher. It's hard to dispatch without one. We're not clairvoyant you know.

froody.invoke.nosuchmethod

You asked for a method that hasn't been registered with this repository.

froody.invoke.nosucherrortype

You asked for a errortype that hasn't been registered with this repository.

froody.invoke.remote

Something went wrong on the remote end of the invokation. This happens when you're using Froody::Implementation::Remote and the remote server returns something like a Server Error or a 404.

froody.response

Somehow the response has become corrupt internally (this should never happen, but since we have a check for it, we have to define an error for it.)

froody.xml

Something went wrong with froody's xml parsing. You probably did something wrong in the XML spec.

froody.xml.invalid

We couldn't parse the XML from the string - i.e. XML::LibXML barfed on the input. I bet it wasn't valid XML.

froody.xml.nomethods

The XML spec you passed in didn't contain any methods.

perl

Errors coming from Perl code, i.e. nothing wrong with what the user has done, but rather there's something wrong with the way the code was written

perl.methodcall

There was a problem with a method call.

perl.methodcall.class

A method was called in object context when it was an instance method.

perl.methodcall.instance

A method was called in class context when it was an object method.

perl.methodcall.param

You called the method with invalid parameters

perl.methodcall.unimplemented

You called ab 'abstract' method that should have been overriden in a concrete base class

perl.use

There was a problem loading a class or requiring some code.

BUGS ^

None known.

Please report any bugs you find via the CPAN RT system. http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Froody

AUTHOR ^

Copyright Fotango 2005. All rights reserved.

Please see the main Froody documentation for details of who has worked on this project.

This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO ^

Froody::Error::Standard, Froody::Response::Error

syntax highlighting: