Javid Jamae wrote:What exactly are you trying to accomplish?
Thank you so much. I'll try to explain.
Actual situation
------------------
We have 2 different applications running in one physical server. Each application is running in a different Tomcat. Both applications are deployed to the ROOT context (/) and use the HTTP and AJP connectors. We use one Apache with mod_jk acting as a proxy for the two applications. We use Apache Virtual Host and Workers are configured for each application depending on the port.
To sum up,
In the physical application server (with the 2 Tomcat) we can access to:
http://server-name.domain.suffix:8080/ (HTTP for application-1)
http://server-name.domain.suffix:8009/ (AJP for application-1)
http://server-name.domain.suffix:8081/ (HTTP for application-2)
http://server-name.domain.suffix:8010/ (AJP for application-2)
In the physical web server (with Apache) we (and everyone in the Internet) can access to:
http://application-1.domain.suffix/ (port 80, HTTP)
http://application-2.domain.suffix/ (port 80, HTTP)
Future ideal situation
------------------------
We move to a
Java EE Application Server. We use EJB and probably Seam (and JPA, Hibernate Search... we are training on this). The "old web applications" are refactored and share application logic through an one or more EJB modules. All are packaged in one EAR and use only Local interfaces.
All the "old URLs" should work. We also want to use Apache server (static files, logs, load balancing) in the other machine.
Thank you so much.