Changes between Version 62 and Version 63 of ProgrammingGuidelines


Ignore:
Timestamp:
05/24/13 11:54:19 (6 years ago)
Author:
welberge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProgrammingGuidelines

    v62 v63  
    3030 1. A chain of exceptions can be used to translate a low-level exception into a higher level one ([[BibCite(bloch2008)]] item 61). When this technique is used, always include the original exception in the higher level exception (using initCause), so that it stack trace can be used in debugging. 
    3131 1. Don't ignore exceptions ([[BibCite(bloch2008)]], item 65). Either catch them and act upon them or throw them. If an exception can't happen, but has to be caught anyways, throw an !AssertionError. If the occurrence of an exception doesn't influence the progress of the client (for example, a file not properly closing after reading all information from it), at least log it. 
     32 
     33== Dealing with Data == 
     34To allow easy jar and webstart deployment, all data required to run your project should be in its resource directory and loaded through hmi.util.Resources/hmi.util.ResourcePool. 
     35See UsingResources for more details on this. 
    3236 
    3337== Asap Logging Setup ==