Unbelievable, but I finally found the time to put together a new release of the ApexLib Framework for Oracle Application Express (APEX).
I have created bug fixes and enhancements since the last version has been released last year, but I just sent them to the person who requested it. I thought it’s really getting time to put together a up-to-date version which also handles some issues with the last Oracle APEX 3.1.1 patchset.
If you are using my Drop in replacement for V and NV function and you are upgrading to Oracle APEX 3.1 then you have to alter the functions to reference the new schema FLOWS_030100!!!
If you are not doing this your applications will not work because the functions are trying to read the session state from the old FLOWS_030000 schema, but there no values can be found for the current session which are stored in FLOWS_030100.
Just to let you know that you are not searching to long why your application doesn’t work after the upgrade.
Note: You may have installed this drop in replacements as optional part of the ApexLib Framework!
According to Richard, a Scottish ApexLib user it does!
He has successfully integrated the ApexLib Framework into a HTMLDB 1.6 application. To get it running you have to follow the APEX 2.0 installation steps.
I have no plans to “officially” support HTMLDB 1.6, because I don’t have such an environment and 4 different APEX versions are already enough, but it’s great to hear that it works with such an old version, too!
As you could see with the ApexLib Feature Demonstration application, the framework is also working on apex.oracle.com. But to be honest, it’s a lot of work to upload all this single packages and views to apex.oracle.com to be able to install them into your schema.
Note: This error only occurs if you have included the ApexLib_Lov.js file into your “Popup Lov Template” as described in Chapter 3.12 of the How To Integrate.
Use the following new version of ApexLib_Lov.js to fix that problem.
Maybe you have already seen that I have released version 1.6 of the ApexLib Framework.
My original plan was to make the “Cascading lov” area feature complete in this release, but I was a little bit lazy on the weekend and was looking at some content management systems for the ApexLib Homepage, instead of doing some programming.
Enhancements to the APEX repository views in Oracle APEX 3.0 made it possible to remove some existing restrictions of the ApexLib framework.
One of the “drawbacks” of using the ApexLib Framework is, that you have to remember all the “ApexLib Hints” which you have to use to configure the runtime behavior of the framework.
Ok, after some time you are getting used to them, but still, wouldn’t it be much more comfortable to set this properties as you do it for the APEX properties?
How often have you already created an APEX validation to make sure that a money amount is greater or egal to 0.00, a percentage value is between 0 and 100 or that an entered date is less or equal to today?
Just uploaded a new release of the Oracle APEX development framework ApexLib onto Sourceforge.
As you can see from the change log, this release contains a lot of bug fixes, but it also includes a new feature. Declarative Min-/Max Value Validation in the Browser. More about that later.