awmurray
2017-12-06 15:49:35 UTC
I'm converting from an old version of TomEE to the newest stable version of
TomEE+ and I think I have most of the problems resolved, except one.
I have been deploying statically with this in $CATALINA_HOME/conf/tomee.xml:
<Deployments jar="C:\app-pathl\myapp-ear\target\exploded-ear-with-2-wars" />
When I start TomEE, it doesn't deploy this app like it used to - previously
it would treat this as an exploded artifact and simply start and work. With
the new TomEE+, it ignores this completely so the app isn't processed by the
deployment process.
When I try to dynamically drop the myapp-ear.ear into
$CATALINA_HOME/webapps, it does this in webapps:
webapps
- myapp-ear.ear
- myapp-ear (exploded directory)
- myapp-ear-war1 (exploded directory)
And fails because of ClassNotFound exceptions in myapp-ear-war1. It should
leave the WARs under the EAR I would think??
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
TomEE+ and I think I have most of the problems resolved, except one.
I have been deploying statically with this in $CATALINA_HOME/conf/tomee.xml:
<Deployments jar="C:\app-pathl\myapp-ear\target\exploded-ear-with-2-wars" />
When I start TomEE, it doesn't deploy this app like it used to - previously
it would treat this as an exploded artifact and simply start and work. With
the new TomEE+, it ignores this completely so the app isn't processed by the
deployment process.
When I try to dynamically drop the myapp-ear.ear into
$CATALINA_HOME/webapps, it does this in webapps:
webapps
- myapp-ear.ear
- myapp-ear (exploded directory)
- myapp-ear-war1 (exploded directory)
And fails because of ClassNotFound exceptions in myapp-ear-war1. It should
leave the WARs under the EAR I would think??
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html