TylerEnv, as a concept, shouldn't be deeply embedded in the code as it is now. It should exist, but it should only be present around the SOAP code, needed because all of the SOAP endpoints we directly talk to are hardcoded in the service XML files. It doesn't need to exist around the database code, as we shouldn't have a database that is serving both production and staging environments at the same time.
Will require some database migrations to change the database columns (i.e. changing the domain column from "illinois-stage" to "illinois"). See https://github.com/SuffolkLITLab/EfileProxyServer/blob/main/proxyserver/src/main/java/edu/suffolk/litlab/efsp/db/DatabaseVersion.java for some examples of how we do database migrations.
Should also keep this in mind for #398: don't copy the existing structure for the new TrueFile database.
Started working on this in 54e17a0.
TylerEnv, as a concept, shouldn't be deeply embedded in the code as it is now. It should exist, but it should only be present around the SOAP code, needed because all of the SOAP endpoints we directly talk to are hardcoded in the service XML files. It doesn't need to exist around the database code, as we shouldn't have a database that is serving both production and staging environments at the same time.
Will require some database migrations to change the database columns (i.e. changing the domain column from "illinois-stage" to "illinois"). See https://github.com/SuffolkLITLab/EfileProxyServer/blob/main/proxyserver/src/main/java/edu/suffolk/litlab/efsp/db/DatabaseVersion.java for some examples of how we do database migrations.
Should also keep this in mind for #398: don't copy the existing structure for the new TrueFile database.
Started working on this in 54e17a0.