Re: Oracle HTTP Server - the future

> Apache is easy to configure and change. For example: I've got the
> Apache server for our development environment sitting in the same box as
> the dev dbs. Recently, I started using 11gr2 in a separate sandbox
> server. To change our Apache server to also service the apex stuff in
> the sandpit db was child's play:
> edit one file, re-start. I'm not sure it'd have been that easy with the
> standalone Apex listener. Although it looks like a good alternative to
> fusion that might not go away soon.

Oracle doesn't want you to "configure and change", Oracle wants you to buy things. I am fairly certain that there will be an "apex configuration add-on module" sometimes in the future, that we will be required to pay for. The right answer is to discard Apex altogether. There are other GUI tools for creating applications, equally as capable as Apex. The price is also the same. I am talking about Cake, Django and Symfony. The all use Apache2, they all can access Oracle, they all can create forms and reports, they are all great alternatives, guaranteed not to go away. Apex is not. The right approach is to install Apex, so that the legacy applications can work, while being migrated to something else. The fabled "mod_plsql Apache module" is outsourced, but the utmost care was taken that it is almost impossible to install and that no clear instructions was ever provided. When I saw that, I knew that Apex is just another road toward a commercial application development tool, something that will eventually have to be purchased. My personal preference is, therefore, Symfony. It's easy to learn, it's very powerful, even more so than Apex and it is free. For the basic stuff, I don't even bother with that, I write it directly in PHP, using ADOdb. Apex is a tool that resolves the problem that is not really important. It allows idiots to write graphically appealing application. I can certainly live without it.

-- 
http://mgogala.byethost5.com