Thanks so much for the info and ongoing education. I think I'm getting there. But please bear with me. I'm still trying to get a handle on how this all works and what the best practices are.
I now understand that TC will take all folders it finds in the appBase folder and deploy them, assuming they are all webapps. I'm assuming from what you said that the default path for each webapp is the folder name in appBase. I realize that this is super easy as long as you don't have any unique things to specify about the deployment such as a database resource. So assuming I need to specify more info about a particular webapp deployment, I can define a context file that augments the deployment info for a particular auto-deployed app in appBase. But from what you said previously regarding the error I was getting, if the webapp is in appBase, I have no choice but to use the appBase's folder name as the context path. Am I correct so far? But if I put the webapp anywhere outside of the appBase folder, I can now create a context file for the app using any desired context path as the name of the context file and point to the webapp, no matter what the name or location using docBase, correct? If my understanding is correct, then fine. I'm one step closer... It does seem strange that I can't alias the context path to get to an appBase webapp using a desired URL. But I'm sure there are reasons, and if that's the way it is, fine. I just need to understand the rules. But all of this did work with path aliasing in 7.0.27 when I just had all of the context tags directly in server.xml. So that's why I'm struggling with the changes to the rules and capabilities. So.... the simple answer as far as doing things correctly in TC is to rename all of my webapps in the appBase folder to match their associated context paths. I will likely head that direction. But I have a pretty complex automated build process that I will need to go into and modify things to get this implemented. Unfortunately, that can't happen overnight. In the meantime, I've got lots of webapps from my earlier, currently working config that use a context path that is different from the appBase folder name. I think I know what I can do. But I want to see if it violates the rules and how bad..... My proposal is to keep the appBase pointing to the webapps folder. And any webapps that have matching paths and names can go there and work fine. Next, until I can change the build process to create the webapps named as the context path, can I create a parallel "webapps2" folder and NOT point appBase to it and put all of the 'misnamed' webapps in there? Then go to the context files for those webapps and fully qualify the docBase (c:\domains\myHost\webapps2\myWebApp1)? I realize this is not the recommended design. But I need a stopgap solution until I can change the build process. So, is this solution at least an "acceptable" one in the interim? If not, what is the best way for me to keep my misnamed webapps that don't match the context path for a while and still keep the lights on? Thanks. Jerry --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
