Once we identify a pattern and are certain it’s going to happen again, our code reuse mentality breaks loose. It’s only a matter of time until we end up with a shiny new tool in our code toolbox. This is especially true when we know that plugging in an existing piece of code can save us significant time and effort the next time around.
The initial development of an ADF Standalone application is such a pattern primed for code reuse. I think anyone would agree that bootstrapping an ADF standalone application becomes a repetitive task. On the other hand agreeing that just performing the initial required setup to start the implementation of the actual project requirements can take significant time and effort might not be as clear.
Let’s go over the initial setup considerations of an ADF Standalone application at a high level to have a basic understanding of why it takes significant time and effort. Among the main goals of an ADF standalone application is to deliver an engaging user experience. There are a lot of aspects to consider when we create a user experience not only visual but also functional. To list a few:
1. Consistent look and feel
2. Layout design
3. Effective user interfaces
Security is an aspect that is often overlooked and underestimated. How to authenticate users with the corresponding login and logout functionality and how to authorize users to access only what they should among other things. From my experiences implementing these aspects I can vouch that it takes significant time and effort.
I must point out an additional benefit of bootstrapping your ADF standalone applications as clients themselves have asked for it. The benefit is standardization of ADF standalone application development within the organization. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.