Home >> All >> allensoft >> [ bug Javadoc ]

•	allensoft.bug.server.* (3)

• allensoft.bug: Javadoc index of package allensoft.bug.


Package Samples:

• allensoft.bug.server

Classes:

• CrashHandler: Handles crashes (uncaught exceptions/errors) by reporting them to the user. By using the CrashReportingThread instead of a java.lang.Thread crashes are automatically reported to the global crash handler to be handled. Typically an application will install a crash handler by calling the install method supplying a name for the program and a version number and an optional BugSubmitter object for submitting crash reports: public static void main (String args []) { // Install crash handler that reports crashes using RMI to a server named "BugServer" // at somehost.somedomain CrashHandler.install ("Test ...
• CrashReportingThread: A Thread sub class that automatically reports any crashes (i.e uncaught exceptions/errors) that occurr during its execution. Use this class in place of the java.lang.Thread class to ensure all threads in your application will report their crashes. This class can be used exactly like the java.lang.Thread class except that instead of overriding the run method you must override the runThread method.
• CrashReportingEventQueue: An event queue that reports any crashes to the global CrashHandler . This can be used to catch exceptions that occur in the AWT event thread. It is identical to the standard event queue but catches any uncaught exceptions and passes them on to the CrashHandler .
• WizardBasedBugSubmitter: A convienient base class for bug submitters. This class provides a means for obtaining information from the user about a bug report (such as the user's email and comments) using a friendly wizard.
• BugReport: A BugReport keeps track of all the details of a bug. This includes information such as the application name and version, the OS name and version and JVM version and vendor etc.
• DefaultCrashHandler: Handles crashes by displaying a CrahReportDialog to inform the user and allowing the user to submitt a bug report if a BugSubmitter has been supplied during construction.
• CrashReport: A type of BugReport which is the result of an uncaught exception/error. A CrashReportingThread will automatically report any uncaught exceptions in this way.
• DatabaseBugServer: A bug server which inserts bug reports into a database. The database can be initialized using the InitDatabase class which will create the required tables.
• BugReportWizard: The base class for bug reporting wizards. This wizard will ask the user for their email address and any comments and fill these in in the bug report.
• BugSubmitter: The base class for all bug reporters. Bug reporters display a message to the user that a bug has occurred.
• InitDatabase: Creates the tables required for storing bugs and crashes in a database as used by the DatabaseBugServer.
• Test: A simple test harness that divides by zero when a button is clicked to test the crash handling classes.
• BugServer: The remote interface to a bug server. The bug server processes bug reports sent to it.
• SubmitBugReportWizard: The base class for bug report wizards that submit a bug report over the internet.
• RMIBugSubmitter: Submits a bug report by connecting to a BugServer object using RMI.
• SaveBugReportWizard: Wizard used to get information about a bug report so it can be saved to a file.
• BugSubmissionException: The exception thrown when there is a problem submitting a bug report.
• TechnicalInfoDialog: Dialog used to display technical information about a crash report.
• CrashReportDialog: A dilaog that displays the details of a crash report to the user.
• EMailBugSubmitter: Submits a bug report by email.

Home | Contact Us | Privacy Policy | Terms of Service