Exploded Deployment woes on Windows

[damianharvey]

I normally use a Mac for my development and haven't had any issues surrounding Exploded Deployment aside from the PermGen thing.

I've come into a client site today and am forced to use a Windows laptop, but I can't unexplode a project as the Application Server has locked a bunch of Jars.

I've tried the antiJARLocking="true" antiResourceLocking="true", however now it doesn't lock the Jars but still holds onto the security.drl file.

Does anyone actually develop on Windows? Do you use Exploded Deployment? If so, how have you resolved this issue?

Thanks,

Damian

[delphi'sghost]

I use Windows and exploded deployment, and am not sure what the problem is.

When I am devloping, if I do a 'clean', it tries to delete everything but some jars are locked. I just ignore that, re-deploy, and all my code is updated even if some of the deployed standard jars are not.

I'm using Jboss 4.05 standard install, with the only config changes being to the log4J config file.

Error messages aside, do you get your app re-deployed when you double click on the 'restart' ant task?

[damianharvey]

It can't unexplode the deployed project while the server is running due to various locks on files. It deletes what it can but leaves the locked files behind. Then when it tries to re-explode it all fails.

[purplahaze]

I have the same problem

[gavin.king]

Yes, this is a problem at the JVM level on windows. Usually, it resolves itself by restarting the AS.