<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Guys the way that we have worked in the past where exploded files just works is a really good feature. One that definitely is a selling point.<div><br></div><div>Reading through the thread higher in the list in the forums I get why we are here today.</div><div><br></div><div>However, burying this change in the META-INF directory seems like a real pain from a usability perspective.</div><div><br></div><div>What about renaming the exploded directory tree instead.</div><div><br></div><div>Copy </div><div>application.war</div><div>to the hot-deploy directory</div><div><br></div><div>rename application.war.dodeploy when you want to deploy it</div><div>rename to aplication.war.doundeloy when you want to undeploy it</div><div><br></div><div>WHen it is is deployed</div><div>application.war.deployed</div><div>application.war.failed with a outtext file in the directory that states the reasons for failure?</div><div><br></div><div>If I do an lS in the directory I can immediately see what is going on. I do not have to bury myself in META-INF directories and I would think this is a lot simpler.</div><div><br></div><div>I did not read all of the pages, this seems like an elegant solution to some of the "Atomicy" issues you have around deployment, along with making this easy to use.</div><div><br></div><div><div>Does this mean that if I update an .jsp page in an exploded directory I need to mark it as .dodeploy?</div><div><br></div><div>Have you guys talked with Max and the tools team to see what/how this effects what they have to do?</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><div>Jim Tyrrell</div><div>Senior JBoss Solutions Architect</div><div><br></div><div>Did you see RHT on CNBC's Mad Money?</div><div><a href="http://www.cnbc.com/id/39401056">http://www.cnbc.com/id/39401056</a></div></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Apr 12, 2011, at 9:42 AM, Jason T. Greene wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Yeah basically we had not finished the feature until Beta2 and onward. I <br>highly recommend grabbing the latest upstream.<br><br>On 4/12/11 10:18 AM, Howard Gao wrote:<br><blockquote type="cite">Thanks Jason. I think I would use auto-deploy for most of the time.<br></blockquote><blockquote type="cite">If by default it is auto-deploy for non-exploded deployment, then I<br></blockquote><blockquote type="cite">think there is an issue with it. I deployed a simple MDB (packed in a<br></blockquote><blockquote type="cite">jar file, I think that's non-exploded) and I still have to add a<br></blockquote><blockquote type="cite">.dodeploy to trigger the processing of my MDB.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Or perhaps it has been just so changed? My as7 is built from the code<br></blockquote><blockquote type="cite">days ago.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Howard<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 04/12/2011 11:10 PM, Jason T. Greene wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Actually allow me to clarify:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">BY DEFAULT you do not need markers for non-exploded deployments.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">You do need them for exploded. You can enable auto-deploy for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">directories, and ignore using any marker, but you have the same casino<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">odds that you had in previous AS releases.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On 4/12/11 10:04 AM, Jason T. Greene wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">You dont need markers for non-exploded deployments (see auto-deploy in<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">deployments/README.txt)<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On 4/12/11 9:51 AM, Howard Gao wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hi,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">In AS7 it uses a bunch of 'Marker files' to control and indicate a<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">deployment. Comparing to previous AS 4 I found this is not so<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">convenient. For example if I want to deploy an EJB jar I need to<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">drop it<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">to the /deployments dir and create a .dodeploy marker file. And if my<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">EJB failed to deploy the marker file changed to .fail mark file. In a<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">debug process this deployment can be repeated many times, each time a<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">.dodeploy has to be manually added. And that's for a single EJB. If I<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">have 5 EJB jars deployed I need file marker files manually created.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">In AS 4 I just drop it and done. I wonder what's the good reason for<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">those marker files? From a user's point of view, for what other<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">purposes<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">could it be to drop something to the deployments directory than for<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">deploying it right away?<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Howard<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">jboss-as7-dev mailing list<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><br><br>-- <br>Jason T. Greene<br>JBoss, a division of Red Hat<br>_______________________________________________<br>jboss-as7-dev mailing list<br><a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br></div></blockquote></div><br></div></div></body></html>