the jar path is ....<war name>/.../jar name so the jar name is impacted by it
locally it passes but i patched xbean as mentionned (hope it will be included next week) that said think a bit more to this feature and i think you don't want to use it: 1) ejb can be share (jndi names) accross the instance so it will fail (jndi name already bound) 2) it deploy version N+1 the undeploy version N -> so the version N can't start anything unique at JVM level (start a server for instance/block a port) 3) same kind of issue with resources.xml 4) if the deployment of v N+1 fails v N is undeployed (IIRC) etc... this is a wrong good idea IMO because easily breakable with updates *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/2/27 zeeman <[email protected]> > Hi, > > The ## is in the WAR file name, none of the jars have # in their names. > Just > to be sure. > > Would it be possible to get it fixed? When Can I try a new build? Many prod > deployments will use parallel deployment and blocked by this. Thanks! > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661048.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
