| perfSONAR_PS-Base documentation | Contained in the perfSONAR_PS-Base distribution. |
perfSONAR_PS::Error::Common - A module that provides the exceptions framework that are common for perfSONAR PS
This module provides the common exception objects.
Base exception object from which all other common exceptions inherit.
Transportation error, such as uncommunicative host, non-resolveable address etc.
Configuration error; such as not valid, cannot be found etc.
No logger can be found
Not sure - from EU
Somethign went wrong with teh daemon architecture
The manager could not find an appropiate configuration file
the manager could not spawn off the relevant service
Common storage exception object. All storage exceptions derive from this.
The query is not valid, or the query is wrong; base object
The data query is incomplete
The metadata query is incomplete
The timestamp in the query is invalid
The update parameter is invalid
The fetch for the data failed.
Could not open the storage component (database etc) required.
An error with updating occured.
Could not delete the appropriate item.
An error with closing the storage component.
Exporter, Error::Simple
To join the 'perfSONAR-PS' mailing list, please visit:
https://mail.internet2.edu/wws/info/i2-perfsonar
The perfSONAR-PS subversion repository is located at:
https://svn.internet2.edu/svn/perfSONAR-PS
Questions and comments can be directed to the author, or the mailing list.
$Id$
Yee-Ting Li <ytl@slac.stanford.edu>
You should have received a copy of the Internet2 Intellectual Property Framework along with this software. If not, see <http://www.internet2.edu/membership/ip.html>
Copyright (c) 2004-2007, Internet2 and the University of Delaware
All rights reserved.
| perfSONAR_PS-Base documentation | Contained in the perfSONAR_PS-Base distribution. |
use perfSONAR_PS::Error; our $VERSION = 0.09;
package perfSONAR_PS::Error::Common; use base "perfSONAR_PS::Error";
package perfSONAR_PS::Error::Transport; use base "perfSONAR_PS::Error"; # configuration and service startup
package perfSONAR_PS::Error::Common::Configuration; use base "perfSONAR_PS::Error::Common";
package perfSONAR_PS::Error::Common::NoLogger; use base "perfSONAR_PS::Error::Common";
package perfSONAR_PS::Error::Common::ActionNotSupported; use base "perfSONAR_PS::Error::Common"; #YTL: i'm guessing the manager maps to our daemon architecture here
package perfSONAR_PS::Error::Common::Manager; use base "perfSONAR_PS::Error::Common";
package perfSONAR_PS::Error::Common::Manager::NoConfiguration; use base "perfSONAR_PS::Error::Common::Manager";
package perfSONAR_PS::Error::Common::Manager::CannotCreateComponent; use base "perfSONAR_PS::Error::Common::Manager"; #YTL: storage related stuff; queryies etc. do we want MA's to subclass these errors? or should the mas # just return these? ie do we need the granularity of each MA having their own error types considering # we can have the specific message of the error as part of the error object
package perfSONAR_PS::Error::Common::Storage; use base "perfSONAR_PS::Error::Common";
package perfSONAR_PS::Error::Common::Storage::Query; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Query::IncompleteData; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Query::IncompleteMetaData; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Query::InvalidTimestampType; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Query::InvalidUpdateParamter; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Fetch; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Open; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Update; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Delete; use base "perfSONAR_PS::Error::Common::Storage";
package perfSONAR_PS::Error::Common::Storage::Close; use base "perfSONAR_PS::Error::Common::Storage"; 1;