I was wrong, the duplicate ID issue is still there, it was just delayed by the previous errors.
The id's have changed per the suggested pattern, but they are still duplicates. Note that the EJB module and WAR resides in the same EAR. That is common practice in other containers, but appears not to be best practice in Tomee? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/DuplicateDeploymentIdException-same-EJB-found-twice-in-claspath-scan-tp4676366p4676375.html Sent from the TomEE Users mailing list archive at Nabble.com.
