In a previous blog post (http://ig.obsglobal.com/2013/09/mind-shift-necessary-when-adopting-oracle-fusion-middleware-part-1/), I talked about the how, with a slight adjustment, we can apply most SOLID principles to Oracle Fusion Middleware design and development. I also alluded to a third hurdle, which is working with limitations.
A couple of years ago, Online began an Enterprise level project with multiple vendors and a total team size of over 500 people. Oracle Fusion Middleware had been selected as the implementation technology. With 14+ years of development experience in traditional development languages such as C\C++, Delphi, C#, and Java, I approached this new technology as I would any of the other languages I’d learned. I attempted to apply SOLID principles and in doing so, realized that there was a mind shift necessary to successfully achieve this goal.