In my previous Post i tried to shed some light on all the different areas ApexLib is covering.
This time I’d like to tell you about the future of the ApexLib Framework on and after Oracle Application Express 4.2.
Long story short: there will be no ApexLib Framework Version for Oracle APEX 4.2
Wait…Why? Whats going on?
Ok, here is the longer version:
Years ago, in the dark ages of Oracle APEX 2.x and 3.x People were longing for Features that APEX didn’t provide at that time (e.g. cascading LOVs). The ApexLib Framework was (due to the lack of Plugins) a comfortable way to workaround those missing Features.
Also many things that the ApexLib Framework provided are now part of APEX itself. And this makes me very happy. ApexLib was never meant to be there forever, it was always a temporary workaround. Now this workaround isn’t necessary anymore. Less and less People are using the ApexLib Framework, most Developers started to use Plugins and DA’s.
So i figured the upcoming release of Oracle APEX is a good opportunity to say “Farewell ApexLib Framework, you help literally thousands of Developers creating better Applications”.
That also means: thanks Patrick, for inventing this wonderful Framework. And thanks to all in the APEX Development Team to make this workaround obsolete.
How do I remove ApexLib Framework from my Application?
If you have an existing Application on APEX 4.x which uses the ApexLib Framework AND plan to upgrade to Oracle APEX 4.2 in the near future (once its released…), then you should start right away to rip ApexLib calls out of your Application and switch to native Features (APEX Errorhandling, Cascading LOVs, TabForm Validations, …) or – where needed – Dynamic Actions and Plugins.
I’m sure there will be some questions in particular situations. Feel free to post a comment or send me a mail to firstname.lastname@example.org .