Well both wars have different names I will try with startup event you Can see some code, not the latest one on github.com/arquillian/arquillian-extension-moco the class MockServerDeployer
If you want I Can send you the logs Enviat des del meu iPhone El 29/04/2014, a les 10.10, Romain Manni-Bucau <[email protected]> va escriure: > Hi > > hmm depends actually how you deploy it. Do you put same names? We can > deploy multiple wars if one is not managed by arquillian more or less. > Typically I used deploy on startup feature a lot for it. > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-04-29 9:45 GMT+02:00 Alex Soto <[email protected]>: >> Hello I am developing an arquillian extension that basically deploys two >> WAR files, the first one automatically and the second one is created by the >> user using @Deployment. >> >> Basically the extensions listens for AfterDeploy annotation and it uses the >> current org.jboss.arquillian.container.spi.Container instance to call the >> deploy method passing as argument one war file resolved by Shrinkwrap Maven >> resolver. >> >> The problem is that when I run the extension with Embedded TomEE next >> exception is thrown: Application cannot be deployed as it contains >> deployment-ids which are in use and points to the WAR deployed by >> extension. If instead of listening AfterDeploy event I listen the >> BeforeDeploy, the WAR that cannot be deployed is the one generated by user >> with @Deployment. >> >> But if I run with Remote (Managed) TomEE then it works perfectly, so it >> seems like we couldn't deploy two war files in embed mode, is it correct? >> >> Thank you so much. >> >> -- >> +----------------------------------------------------------+ >> Alex Soto Bueno >> www.lordofthejars.com >> +----------------------------------------------------------+
