Hi why don't you simply put your app in apps/ (same level as webapps - can need to be created) then activated the commented line in tomee.xml. Start/stop/restart will keep it.
We had the issue tomee.sh deploy was keeping the apps so it is no more activated by default (i don't recall the jira but it is traced). More on it here http://openejb.979440.n4.nabble.com/TomEE-1-5-2-EAR-server-restart-issue-td4662692.html *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/8/28 Christian Schlichtherle <[email protected]> > Hi, > > after all the frustration with 1.5.2, I downloaded and tried the latest > 1.6.0-SNAPSHOT of TomEE+. I can deploy and undeploy my WARs and EARs and > got rid of this InternalError when using JMS. However, when my apps are > deployed, then after a restart, TomEE+ has forgot all deployed apps. > > On another note: When using > > bin/tomee.sh start > > then after that I can't do > > bin/tomee.sh deploy $file > > because it says it can't connect. This applies to 1.5.2 and 1.6.0-SNAPSHOT. > > And yet another issue: > > I can't use > > bin/tomee.sh deploy -u $file > > at all because it doesn't understand the -u option - as opposed to > OpenEJB. So I have to undeploy/deploy all the time. This applies to 1.5.2 > and 1.6.0-SNAPSHOT. > > Regards, > Christian Schlichtherle > >
