Jim and I were discussing exploded deployments in #torquebox, and realized...
TorqueBox pretty much only uses exploded deployments, but we do it slightly differently,
and avoid copying tons of files around and dealing with partial-copies and non-atomic
things.
Our exploded apps live wherever the user wants them to live. Anywhere on disk.
Into the deployments/ directory, we scribble a simple text file, which is basically a
poor-man's symlink, plus other information used by TorqueBox.
But generally, it contains a path-to-the-exploded-app.
A deployer picks it up, and adjusts the DEPLOYMENT_ROOT (or whatnot) to point to the
actual exploded application elsewhere on disk.
From the AS perspective, we're deploy 1 small text file, at least
initially. But then it magically becomes an exploded directory full of loose files.
Dunno if it'd help, but generally supporting a deployments/myapp.link deployment,
where the myapp.link file is just a text file containing only and exactly the path to an
exploded application, might be useful.
-Bob
On Jul 11, 2011, at 11:00 AM, Jason T. Greene wrote:
On 7/11/11 9:41 AM, Max Rydahl Andersen wrote:
> Brian,
>
>> This is merged (thanks!) along with a fix such that deleting the
>> deployment content triggers undeploy[1].
>>
>> [1]
https://issues.jboss.org/browse/AS7-1240
>
> For clarification - does this "undeploy on deleted content" only apply to
zipped archives
> or will it also happen for exploded ?
>
> And I assume deleting the .deploy will work in any case?
>
It only applies to things which have auto-deploy turned on. So not by
default for exploded. Although you could turn it on and get russian
roulette deployment. The biggest problem being that frameworks are
surprised when their content disappears before being shutdown. This isnt
an issue for archives because we make a copy.
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev