[jboss-as7-dev] persistence of deployment action updates

Brian Stansberry brian.stansberry at redhat.com
Thu Jan 20 11:51:41 EST 2011


LOL. That's being considered. But we'll still want to persist somewhere. :)

On 1/20/11 9:52 AM, Max Rydahl Andersen wrote:
> Damn - was so close on having a xml file that didn't had to be cleaned out before copying to another server without deployments ;)
>
> /max
>
> On Jan 20, 2011, at 16:14, Brian Stansberry wrote:
>
>> If you can figure out why they aren't persisted, I'd appreciate it. It
>> may not be worth fixing if the detyped conversion is going to change
>> that area, but we should understand why it broke so we can make sure its
>> fixed once the detyped handling is in. It wasn't intentional.
>>
>> On 1/19/11 4:17 PM, Alexey Loubyansky wrote:
>>> I noticed that deployment actions successfully executed using the
>>> deployment manager api are not persisted any more (I remember they used
>>> to be). The content is still there in the data dir but the config file
>>> although touched (the timestamp is updated) but the deployments
>>> themselves aren't there in xml.
>>>
>>> I talked about this to Emanuel today and wanted to mention it to
>>> everybody. I could look into that but Emanuel said that maybe it's
>>> better to wait until the detyped stuff has been merged into master.
>>>
>>> Alexey
>>> _______________________________________________
>>> 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
>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat



More information about the jboss-as7-dev mailing list