Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We tend to create our most important application specific runtime exception classes with some special constructors, some constants and a ResourceBundle.</p> <p>Example snippet:</p> <pre><code> public class MyException extends RuntimeException { private static final long serialVersionUID = 5224152764776895846L; private static final ResourceBundle MESSAGES; static { MESSAGES = ResourceBundle.getBundle("....MyExceptionMessages"); } public static final String NO_CODE = "unknown"; public static final String PROBLEMCODEONE = "problemCodeOne"; public static final String PROBLEMCODETWO = "problemCodeTwo"; // ... some more self-descriptive problem code constants private String errorCode = NO_CODE; private Object[] parameters = null; // Define some constructors public MyException(String errorCode) { super(); this.errorCode = errorCode; } public MyException(String errorCode, Object[] parameters) { this.errorCode = errorCode; this.parameters = parameters; } public MyException(String errorCode, Throwable cause) { super(cause); this.errorCode = errorCode; } public MyException(String errorCode, Object[] parameters, Throwable cause) { super(cause); this.errorCode = errorCode; this.parameters = parameters; } @Override public String getLocalizedMessage() { if (NO_CODE.equals(errorCode)) { return super.getLocalizedMessage(); } String msg = MESSAGES.getString(errorCode); if(parameters == null) { return msg; } return MessageFormat.format(msg, parameters); } } </code></pre> <p>In the properties file we specify the exception descriptions, e.g.:</p> <pre><code> problemCodeOne=Simple exception message problemCodeTwo=Parameterized exception message for {0} value </code></pre> <p>Using this approach</p> <ul> <li>We can use quite readable and understandable throw clauses (<code>throw new MyException(MyException.PROBLEMCODETWO, new Object[] {parameter}, bthe)</code>)</li> <li>The exception messages are "centralized", can easily maintained and "internationalized"</li> </ul> <p><strong>EDIT:</strong> change <code>getMessage</code> to <code>getLocalizedMessage</code> as Elijah suggested.</p> <p><strong>EDIT2:</strong> Forgot to mention: this approach does not support Locale changing "on-the-fly" but it is intentional (it can be implemented if you need it).</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is a good way to pass useful state information to an exception in Java?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCsaba_H
    1. USCsaba_H
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is a good way to pass useful state information to an exception in Java?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't think one should internationalize the exception texts. Error messages that are shown on the GUI are different, but exceptions should be as simple as possible. What happens if the ResourceBundle could not be read?
      singulars
      1. PO
      1. USTim Büthe
    2. COThen why does the Java exception object have the getLocalizedMessage() method?
      singulars
      1. PO
      1. USElijah
    3. CO@Elijah: thanks for your comment. I have changed the snippet. @Tim: maybe for some it is not a good practice, but we use the Exception message in the logs _and_ on gui-s because we want to avoid "boilerplate code" to transform exceptional situations for humans. I think the Exception message is just for that :) For the ResourceBundle: it is the same problem as for logging or application configuration cannot be read. You should provide a "default" properties for unhandled locales and you should test your application packages carefully.
      singulars
      1. PO
      1. USCsaba_H
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload