Databases
StackOverflow2013
Postsdbo
POHow to avoid using try...catch blocks
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to avoid using try...catch blocks
    primarykey
    data
    text
    <p>I understand these are necessary...of course to write proper code, but is there a design pattern that will help avoid having to repeat try...catch blocks repeatedly in a class? For instance, I wrote a particular class that throws 5 different exceptions.</p> <pre><code>public void iterateComparatorResults(ArrayList&lt;ComparatorValue&gt; results) throws IOException, IllegalArgumentException, IntrospectionException, IllegalAccessException, InvocationTargetException { Iterator&lt;ComparatorValue&gt; iterator = results.iterator(); for(int i=0; i&lt;results.size(); i++) { //Set data variables. setBeans(results.get(i).getClientBean(), results.get(i).getServerBean()); setValues(results.get(i).getClientValue(), results.get(i).getServerValue()); if(results.get(i).isMatch()) { //Data matches. runIteratorTrueAction(); } else if(results.get(i).getInnerBeans() != null){ //Value is a nested bean. Iterate again. ArrayList&lt;ArrayList&lt;ComparatorValue&gt;&gt; innerResults = results.get(i).getInnerBeans(); for(int r=0; r&lt;innerResults.size(); r++) { iterateComparatorResults(innerResults.get(r)); } } else { //Data does not match. runIteratorFalseAction(); } } } </code></pre> <p>Everytime I reference this particular method is any other class, I have to use a try catch block that looks like this. </p> <pre><code>try { beanComparator.setIteratorFalseAction(falseAction); beanComparator.iterateComparatorResults(beanComparator.compareBeans(contact, compareContact)); } catch (IllegalArgumentException e) { e.printStackTrace(); } catch (IOException e) { e.printStackTrace(); } catch (IntrospectionException e) { e.printStackTrace(); } catch (IllegalAccessException e) { e.printStackTrace(); } catch (InvocationTargetException e) { e.printStackTrace(); } </code></pre> <p>I am hoping there is some design pattern I can implement so I can create a separate class or something and hide all the try blocks in one place then reference that class and use the try blocks without actually having to write them. Similar to the way that other frameworks like Spring do? I just need a little direction on how to do this as I have no idea even where to begin.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USryandlf
    1. USryandlf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to avoid using try...catch blocks
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to avoid using try...catch blocks
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to avoid using try...catch blocks
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan't you put these lines in a method..? And instead of repeating them, call that method with specific arguments (i.e. method name to invoke, parameters to pass to that method, etc.).
      singulars
      1. POHow to avoid using try...catch blocks
      1. USMudassir
    2. COYou shouldn't need to catch IllegalArgumentException unless you expect it to happen frequently, since it's a `RuntimeException`.
      singulars
      1. POHow to avoid using try...catch blocks
      1. USLouis Wasserman
 

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