Sorry for not responding for quite long time on this. Yes, you are right, you need to use tomee.sh for that to reproduce the issue.
Exact steps are: 1. Deploy application MBP-Almos:testear2 tomee.sh deploy /tmp/eartest-0.0.1-SNAPSHOT.ear 2. Check jsp page/servlet MBP-Almos:testear2 wget http://localhost:8080/frontend/test.jsp -O - <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Client</title> <body> test page </body> 3. Undeploy application tomee.sh undeploy /Work/java/apache-tomee-plus-1.0.0/apps/eartest-0.0.1-SNAPSHOT/ 4. Check servlet/jsp page availability wget http://localhost:8080/frontend/test.jsp -O - <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Client</title> <body> test page </body> It's still available. Tries to access EJB results in the error messages stated above. -- View this message in context: http://openejb.979440.n4.nabble.com/DuplicateDeploymentIdException-when-deploying-ear-with-application-xml-tp4655362p4655796.html Sent from the OpenEJB User mailing list archive at Nabble.com.
