<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Re: Thoughts on filesystem action driven hot deployment
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/brian.stansberry">Brian Stansberry</a> in <i>JBoss AS7 Development</i> - <a href="http://community.jboss.org/message/592847#592847">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>The foo.war.deployed was a mistake; it's now .isdeployed as we discussed in Antwerp. I told Rob I was going to do that.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The deployment-scanner branch has been pushed upstream. So any further work on this will happen from master.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The standalone/deployments dir now includes a README.txt with the following content:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The standalone/deployments directory in the JBoss Application Server </p><p>distribution is the location end users can place their deployment content </p><p>(e.g. war, ear, jar, sar files) to have it automically deployed into the server </p><p>runtime.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Users, particularly those running production systems, are encouraged to use the </p><p>JBoss AS management APIs to upload and deploy deployment content instead of </p><p>relying on the deployment scanner subsystem that periodically scans this </p><p>directory.  See the JBoss AS documentation for details.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The filesystem deployment scanner in AS 7 and later works differently from </p><p>previous JBoss AS releases. The scanner will no longer attempt to directly </p><p>monitor the deployment content and decide if or when the end user wishes </p><p>the content to be deployed. Instead, the scanner relies on a system of marker </p><p>files, with the user's addition or removal of a marker file serving as a sort</p><p>of command telling the scanner to deploy, undeploy or redeploy content.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The marker files always have the same name as the deployment content to which</p><p>they relate, but with an additional file suffix appended. For example, the </p><p>marker file to indicate the example.war should be deployed is named </p><p>example.war.dodeploy. Different marker file suffixes have different meanings.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The relevant marker file types are:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>.dodeploy     -- Placed by the user to indicate that the given content should </p><p>                 be deployed into the runtime (or redeployed if already </p><p>                 deployed in the runtime.)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>.deploying    -- Placed by the deployment scanner service to indicate that it </p><p>                 has noticed a .dodeploy file and is in the process of </p><p>                 deploying the content. This marker file will be deleted when </p><p>                 the deployment process completes.</p><p>              </p><p>.isdeployed   -- Placed by the deployment scanner service to indicate that the </p><p>                 given content has been deployed into the runtime. If an end </p><p>                 user deletes this file, the content will be undeployed.</p><p>               </p><p>.faileddeploy -- Placed by the deployment scanner service to indicate that the </p><p>                 given content failed to deploy into the runtime. The content </p><p>                 of the file will include some information about the cause of </p><p>                 the failure.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>.undeploying  -- Placed by the deployment scanner service to indicate that it </p><p>                 has noticed a .isdeployed file has been deleted and the </p><p>                 content is being undeployed. This marker file will be deleted </p><p>                 when the undeployment process completes.</p><p>              </p><p>.undeployed   -- Placed by the deployment scanner service to indicate that the </p><p>                 given content has been undeployed from the runtime. If an end </p><p>                 user deletes this file, it has no impact.</p><p>                 </p><p>Basic workflows:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>All examples assume variable $AS points to the root of the JBoss AS distribution.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>A) Add new zipped content and deploy it:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. cp target/example.war/ $AS/standalone/deployment</p><p>2. touch $AS/standalone/deployment/example.war.dodeploy</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>B) Add new unzipped content and deploy it:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. cp -r target/example.war/ $AS/standalone/deployment</p><p>2. touch $AS/standalone/deployment/example.war.dodeploy</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>C) Undeploy currently deployed content:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. rm $AS/standalone/deployment/example.war.isdeployed</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>D) Replace currently deployed zipped content with a new version and deploy it:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. cp target/example.war/ $AS/standalone/deployment</p><p>2. touch $AS/standalone/deployment/example.war.dodeploy</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>E) Replace currently deployed unzipped content with a new version and deploy </p><p>   it:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. rm $AS/standalone/deployment/example.war.isdeployed</p><p>2. wait for $AS/standalone/deployment/example.war.undeployed file to appear</p><p>3. cp -r target/example.war/ $AS/standalone/deployment</p><p>4. touch $AS/standalone/deployment/example.war.dodeploy</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>F) Redeploy currently deployed content (i.e. bounce it with no content </p><p>   change):</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. touch $AS/standalone/deployment/example.war.dodeploy</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/592847#592847">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss AS7 Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>