We used to deploy using cargo to a remote Wildfly server. After several deployments, the web server will run out of heap space which is quite a common problem, and we would need to manually restart the server. On top of that, the reconfiguration for production happens at war assembly and we had no way to reconfigure the artifact for different environments.
Right now, we have a setup where every time a commit is made to the repository, a builder machine will try to build, test, generate exploded war, copy to a base Wildfly docker image, and publish the built image to a private registry. It made life really easier. Cheers, Willie > On 7 Nov 2016, at 6:46 AM, Bilgin Ibryam <[email protected]> wrote: > > Hi all, > > I was wondering what is the most common way for running isis apps? > I know while developing I can use jetty plugin or the WebServer > classes, but what about for running it on other environments? > > For my semat app I have used the .war file in a tomcat instance. And > ll that in a docker container. > You can see my pom.xml used for building docker container and running > at [1] and the demo app running at [2] > > Also noticed that with tomcat 9 the app was throwing lot's of errors > with some not allowed cookie values, so moved back to tomcat 7. > > Is anyone running isis w/o a web container, as standalone Java app? > How do you package the app in the case? > > > [1] https://github.com/bibryam/semat/blob/master/pom.xml > [2] http://semat.ofbizian.com/ > > Cheers, > > -- > Bilgin Ibryam > Camel Committer at ASF & Integration Architect at Red Hat > Blog: http://ofbizian.com | Twitter: @bibryam > > Camel Design Patterns https://leanpub.com/camel-design-patterns > Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475
