alma::acs::callbacks::Objects::MyAcsJException Class Reference
Inheritance diagram for alma::acs::callbacks::Objects::MyAcsJException:
Collaboration diagram for alma::acs::callbacks::Objects::MyAcsJException:
Public Member Functions | |
| MyAcsJException (Throwable cause) | |
| UserException | toCorbaException () |
Protected Member Functions | |
| int | getErrorType () |
| int | getErrorCode () |
Detailed Description
Wraps an arbitrary Throwable in an AcsJException. TODO HSO 2006-08-17: why do we not use a generated subclass of AcsJException, e.g. one from module acserrTypes ?
Constructor & Destructor Documentation
| alma::acs::callbacks::Objects::MyAcsJException::MyAcsJException | ( | Throwable | cause | ) | [inline] |
Member Function Documentation
| int alma::acs::callbacks::Objects::MyAcsJException::getErrorCode | ( | ) | [inline, protected, virtual] |
Forces a subclass to choose an ACS error code.
- Returns:
- the error code
Implements alma::acs::exceptions::AcsJException.
| int alma::acs::callbacks::Objects::MyAcsJException::getErrorType | ( | ) | [inline, protected, virtual] |
Forces a subclass to choose an ACS error type.
- Returns:
- the error type
Implements alma::acs::exceptions::AcsJException.
| UserException alma::acs::callbacks::Objects::MyAcsJException::toCorbaException | ( | ) | [inline, virtual] |
Creates a CORBA UserException from this exception.
Subclasses must return their associated UserException with an ErrorTrace member.
By convention, subclasses must also implement another method that returns the correct subtype of UserException. No problem with a code generator of course...
Implements alma::acs::exceptions::AcsJException.
The documentation for this class was generated from the following file:
