Travel::Routing::DE::EFA::Exception3pm
Travel::routing::de::efa exceptions
Overview
All Exceptions thrown by Travel::Routing::DE::EFA are Travel::Routing::DE::EFA::Exception objects created by Exception::Class(3pm).
See Exception::Class::Base(3pm) for their common methods.
List of exceptions
Travel::Routing::DE::EFA::Exception::Setup
An argument to new had an invalid format.
Additional methods:
$exception->option
|
The option in which the error occurred. |
|---|---|
$exception->have
|
The argument we got. |
$exception->want
|
What kind of argument we want. |
Travel::Routing::DE::EFA::Exception::Net
The HTTP request to the efa interface failed. Contains an HTTP::Response(3pm) object describing the error in http_response.
Travel::Routing::DE::EFA::Exception::NoData
We got no parsable data from the EFA service
Travel::Routing::DE::EFA::Exception::Ambiguous
Our request contained ambiguous data. post_key contains the relevant POST key and post_value the corresponding input value. possibilities is a pipe-separated string of acceptable values reported by the EFA service.
Travel::Routing::DE::EFA::Exception::NoConnections
The EFA service found no connections for our request.
Releases
6 releases since Debian 8 (Jessie); the text changed 5 times.