I was wondering, if someone might help me to better understand how APEX imports a packaged application.
The typical packaged application file looks like a simple SQL*Plus Script that needs to be processed by SQL*Plus from PL/SQL on the server.
I would be most interested to understand how APEX handling this process because it might really help me (and probably many others) to improving our own installation process.
Thank you in advance for any information!
I have reviews the documentation you have pointed me to but i did not find any information about the internals of APEX.
I'm interested on how APEX internally manages to process SQL Scripts that is initially located on a client with SQL*Plus from PL/SQL.
Why exactly? It works like a black box.. Sometimes it is better to let it be then question why it works the way it does..
On the road of life...There are 'windshields', and there are 'bugs'
If this question is answered, please mark the thread as closed and assign points where earned..
The why is as follows:
We had to implement a very similar process for our own installation process and it would be most interesting to understand how Oracle solved this problem in Oracle.
I know quite a few people that implemented server based SQL Script processing from PL/SQL in many different ways (Java, Scheduler, pipes, etc.) and all of the solutions are quite complicated, so I would find it useful to see how APEX has solved this common problem.
This is not about changing the APEX installation process but rather on how to learn from APEX.