Oracle Designer – a tip for Generation of Forms – Enforce Post Generation

0

During our session on the Future of Oracle Designer yesterday I had a conversation with Josef Megens of Oracle Consulting and told me of a trick conceived by Mark Vahsen (formerly of Oracle) to ensure that post-generation changes could not be overlooked after generating a form.

The trick is this: include a program unit called POST_GENERATION_CHANGES in each form – or rather in each Module Definition in Designer – that requires post-generation changes. Make sure that this program unit contains a description of all post-generation changes. Also make sure that it does not compile! This means that when a developer generates the form and forgets to apply post-generation changes, compilation of the form will fail with an error message saying something like ‘Compilation of POST_GENERATION_CHANGES failed’. This should be a clear indication to the developer that he or she should apply the post generation changes.

Share.

About Author

Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director for Fusion Middleware. Consultant, trainer and instructor on diverse areas including Oracle Database (SQL & PLSQL), Service Oriented Architecture, BPM, ADF, Java in various shapes and forms and many other things. Author of the Oracle Press book: Oracle SOA Suite 11g Handbook. Frequent presenter on conferences such as JavaOne, Oracle OpenWorld, ODTUG Kaleidoscope, Devoxx and OBUG. Presenter for Oracle University Celebrity specials.

Comments are closed.