Taking Care – Error Handling - Applied SOA Patterns on the Oracle Platform - page 514

tion. Quite soon, business logic will silently sneak into this handler as well, and
why not? It's fast, simple, and understandable for all Java coders. Do we need to
explain where the catch is? (Refer back to Chapter 1 , SOA Ecosystem - Intercon-
nected Principles, Patterns, and Frameworks ; check all the principles and the ini-
tial CTU's SOA status.)
4. The policies are preloaded on startup for best performance. That's surely a decent
thing to do. Therefore, we have two concerns here: naturally, your policy size
matters (and not always positively), and secondly, you have to restart/redeploy
your application every time you update your policies. This is another reason to
perform the service-error mapping exercise we started with results presented in an
Excel spreadsheet.
Yet again, OFM fault policies are brilliant and the concerns expressed in the preceding
points should not prevent you from using them for static compositions. Just follow the
proposed rules and generic SOA principles/patterns.