yes i confirm that jbillin run in this tow mode ; in my case , i generate
the war file then i deploy it in my tomcat , then i have specified a
JBILLING_HOME env var
for exemple JBILLING_HOME=/opt/jbillingConf
to let jbbilling read it's config file .properties from an external files
located under my JBILLING_HOME , i have to run my tomcat from my JBILLING_HOME
if i run my tomcat with this manner , on the log it write that jbilling is
reading conf from JBILLING_HOME , otherwise it will read conf file from
class Path .
in dev mode it 's normal that i read from class path but in prod mod , i
have to read from an external file ...
I am using JBilling 4.1.1 I build the version from source. I can't see any option to generate a war file. If you have the same version, then can you please share the steps to generate the war file, and what configuration can you store in JBILLING_HOME, please provide an example .property file.
to generate the war file i tape the command "prod war" on the
grails prompt ,
the i deploy this war on a tomcat ,
for example my tomcat is under /opt/tomcat
then my JBILLING_HOME is set to /opt/jbilling_home where i put all
the conf directory from source , and all resources like compiled
report , then to run my tomcat server i open my console from my
jbillinh_home dir , and i run ./../tomcat/bin/startup.sh .... on
the tomcat log you will notice a log indicating that jbillinh is
reading configuration from JBILLING_HOME ,
if it write on the log that jbiilinh is reading configuration from
classpath , that mean that is reading from conf file embedded on
the war file ....
otherwise there is a script under the scripts directory named
PackageRelease , if you run it it will generate a zip file
containing the war and all resources , i have not tested deploying
from this archive :)