a***@lexisnexis.com
2017-11-16 17:06:15 UTC
I'm upgrading an application dev environment to Tomee7.0.2.
We used to have a webapps/tomee.war which parsed the tomee.xml file and
deployed the apps.
Now, I see the tomee.xml file being processed by seeing the logs and classes
scanned by the app class loaders created during Tomcat startup, but they
don't actually start the webapp.
I was told I may have to deploy them in Tomcat (somehow). Preferably a
static deploy would be best which is the way it was working before.
These are the lines from tomee.xml that define the EAR and 3 WARs:
<Deployments jar="C:\home\myapp\ear\target\myapp" />
<Deployments dir="C:\home\myapp\path-to-war1\target\exploded-war1" />
<Deployments dir="C:\home\myapp\path-to-war2\target\exploded-war2" />
<Deployments dir="C:\home\myapp\path-to-war3\target\exploded-war3" />
Any ideas are greatly appreciated... Thanks in advance.
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
We used to have a webapps/tomee.war which parsed the tomee.xml file and
deployed the apps.
Now, I see the tomee.xml file being processed by seeing the logs and classes
scanned by the app class loaders created during Tomcat startup, but they
don't actually start the webapp.
I was told I may have to deploy them in Tomcat (somehow). Preferably a
static deploy would be best which is the way it was working before.
These are the lines from tomee.xml that define the EAR and 3 WARs:
<Deployments jar="C:\home\myapp\ear\target\myapp" />
<Deployments dir="C:\home\myapp\path-to-war1\target\exploded-war1" />
<Deployments dir="C:\home\myapp\path-to-war2\target\exploded-war2" />
<Deployments dir="C:\home\myapp\path-to-war3\target\exploded-war3" />
Any ideas are greatly appreciated... Thanks in advance.
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html