D
dbeavon
Guest
OK, I'll give it a shot. Thanks for the tip. My end goal is this. I have a single project "CoolAppProjectCode" with a code module in it that compiles different r-code depending on the schema. It may connect to one version of the database or another (say coolapp_db_v1_1, and coolapp_db_v1_2). For each of those two, there needs to be a different deployment of code, and potentially a different PROPATH, working directory, etc. Hope this is clear. I thought I would be able to deploy that project twice within the same tomcat instance but it is proving very challenging. In the first place, PDSOE seems to be unaware of "ABL applications" and always deploys to an ABL Application with the same name as the instance, even though my "Servers" definition in PDSOE was defined using another uniquely named "ABL Application". The next problem with deployments from PDSOE is that my deployed modules are "flattened" into the "catalina.base" without regard to my selected "ABL Application" or even "ABL web app name". In other words, all of the ABL code that is deployed to the same TomCat instance will co-habitate in the same folder ({catalina.base}\openedge) without any kind of *separation* that might help uniquely identify it: the project name ("CoolAppProjectCode") or "ABL Application" or "ABL WebApp". So to make a long story short, I can't get the same project (albeit different r-code) to be deployed into the same tomcat instance, whether I am pointing at a new "ABL Application" or not. Based on my limited understanding of "ABL Applications", this should be one of the scenarios for using them.
Continue reading...
Continue reading...