Cleanup JBossAS deploy dir on redeploy of EAR

pdhaigh Aug 26, 2007 6:48 AM

Hi,

I've noticed an oddity since moving to Seam 2.0 from CVS.. Applications using this version, when deploying their EAR file, do not remove the old exploded ear-contents files from {serverhome}/tmp/deploy/

tmp16401sundial.ear-contents
tmp16402sundial.ear-contents
tmp16403sundial.ear-contents
tmp16476sundial.ear-contents
tmp16483sundial.ear-contents
tmp16535sundial.ear-contents
tmp16536sundial.ear-contents
tmp16537sundial.ear-contents
tmp16547sundial.ear-contents

As you can see this leaves multiple exploded ear directories in the deploy dir. This doesn't appear to cause any problems, but I'm pretty sure it didn't happen with Seam 1.2.1 apps... (!)

cheers

phil

1. Re: Cleanup JBossAS deploy dir on redeploy of EAR

pmuir Aug 27, 2007 11:50 AM (in response to pdhaigh)

This doesn't sound right - in default/server/deploy? on JBoss AS 4.2?
Actions
2. Re: Cleanup JBossAS deploy dir on redeploy of EAR

pdhaigh Aug 27, 2007 11:58 AM (in response to pdhaigh)

in /server/default/tmp/deploy .... on 4.2.0.GA yes.
Actions
3. Re: Cleanup JBossAS deploy dir on redeploy of EAR

pmuir Aug 27, 2007 12:02 PM (in response to pdhaigh)

Ah ok. I guess this is related to changing from JBoss AS 4.0 to 4.2... Perhaps ask on a AS forum?
Actions
4. Re: Cleanup JBossAS deploy dir on redeploy of EAR

pdhaigh Aug 27, 2007 12:07 PM (in response to pdhaigh)

ok, will do.

I *thought* that it had been fine for Seam 1.2.1 apps on AS 4.2.0, but I can't be 100% sure, and it's not worth the backtracking to find out - as I say, it doesn't seem to actually cause any harm!
Actions

Go to original post