This content has been marked as final. Show 1 reply
Jose A. wrote:You can go so far using mod_proxy and mod_rewrite, but you hit problems on a number of fronts:
Internet --- Machine1 (Apache like Proxy Reverse and rewrite) --- MAchine2 (GLASSFISH-APEX LISTENER 2.0.1) --- DATABASE
That application will be like a directory of products, we need a nice indexation inside google, yahoo, etc...
We want to build an application with APEX, with a nice custom URL. like http:\\domain\pagina1\pagina2\pagina3
- APEX likes to rewrite URLs to include the session identifier
- All URLs within HTML pages generated by APEX will use the standard APEX style URLs
- Similarly all HTML form actions will use standard APEX URLs
On the plus side APEX does allow you to specify page aliases rather than just numeric identifiers for pages.
Having said that I'd recommend posting on the APEX forum to see if there are any suggestions from the APEX experts there.
One thing I have seen done previously was to write a script that crawled the dynamic APEX site, scraped and cached the generated HTML mapping each page to 'friendly' URLs, and then serving those cached static html pages via Apache, nginx, whatever. Works fine for scenarios where the HTML data changes slowly, say a couple of times a day. On the plus side, it's much more performant/efficient to serve static html, than generating pages dynamically, on the downside you lose the dynamism and interactivity of dynamic html. But still the approach reaches a happy mid ground for many public read-mostly sites, you still have the ease of development of APEX plus the performance characteristics of serving static html.