Mantis - Resin
Viewing Issue Advanced Details
320 minor always 07-19-05 00:00 11-30-05 14:42
user316  
 
normal  
closed 3.0.13  
3.0.13 fixed  
none    
none 3.0.15  
0000320: Issue related to "web-app" configuration in resin 3.x
RSN-364
Not sure if this is a bug or issue related to configuration.
But I was not able to find any resolution related to this issue in the documentation or on the site.

Assume that the name of the web application (or rather the .war file is "abc.war" which gets extracted as 'abc' when server is started.)

In resin 3.x when a web application is configured using different URL prefix, as follows
<web-app id='/xyz' document-directory='webapps/abc' > still after restarting resin we are able to access webedge application using 2 URLs:
1. http://machineName:port/xyz [^]
and
2. http://machineName:port/abc [^]

Actually when only one defination is present (1 st one in this case). So second URL should not work.

Note: The 'Directory listing is disabled' since that entry is not been added to the resin conf file.

Some investigations:
Noticed that <host-default> contains an entry as <web-app-deploy path='webapps'/>. When this entry is removed then the above issue is not seen. But we cannot remove 'web-app-deploy' entry since then a '.war' file will not get extracted when resin is started. So that entry is required for '.war' expansion.
Resin on Solaris

Notes
(0000366)
ferg   
07-19-05 00:00   
The configuration you want is probably:

<web-app id="/xyz" document-directory="abc" archive-path="/opt/wars/foo.war"/>

In other words, you can move the foo.war out of the webapps directory.

Still, this is still a bug since the given configuration should override the context-path for the document-directory.
(0000367)
ferg   
07-19-05 00:00   
server/10tm
(0000368)
user316   
07-19-05 00:00   
Thanks a lot Scott for your updates related to this issue.

Thanks & Regards
Abhijit