[jboss-as7-dev] Intended deployemnt behavior?

[Max Rydahl Andersen]

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?

/max

> 
> On 7/10/11 9:34 AM, Jaikiran Pai wrote:
>> I have fixed this issue https://issues.jboss.org/browse/AS7-1237 here
>> https://github.com/jaikiran/jboss-as/commits/AS7-1237 and sent a pull
>> request.
>> 
>> Brian, could you please review it and push it to upstream, if it looks
>> OK? Manual and unit tests with that fix worked fine for me.
>> 
>> -Jaikiran
>> On Friday 08 July 2011 07:08 PM, Bill Burke wrote:
>>> Maybe I'm just not supposed to do it this way but:
>>> 
>>> 1) I deployed a bad war, bot a deployment error
>>> 2) I fixed the problem, re-copied the war to the deployments directory
>>> 3) The war deployment was skipped on restart (I'm guessing because there
>>> is a mywar.war.failed file in the deploy directory.
>>> 
>>> Is this intended behavior?  Seems like it could cause a lot of problems.
>>>    In the minimum, AS7 should check to see if the date of the .failed or
>>> .deployed file is older than the actual deployment file.
>>> 
>>> I'll log a JIRA if u agree.
>>> 
>> 
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> 
> 
> -- 
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

/max
http://about.me/maxandersen