[jboss-as7-dev] Intended deployemnt behavior?

[Jim Crossley]

Bob McWhirter <bmcwhirt at redhat.com> writes:

[...]

> 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.

Other benefits include:

1) no complicated marker file extension state machine required.  

2) it opens the door for us to deploy things that don't necessarily
match "^.*\\.[SsWwJjEeRr][Aa][Rr]$", e.g. our torquebox .knob files.

Yes, I know the expression is a "standard" (or is it? are .sar's
standard?), but it seems arbitrarily restrictive to those of us desirous
of the JBoss awesomeness without all the JEE goo.  :)

Jim

>
> 	-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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev