Pinned topicWASCE 3.0 Can't deploy as unpacked WAR

‏2011-11-03T20:13:04Z
|Tags:

Answered question
This question has been answered.

Unanswered question
This question has not been answered yet.

I'm trying to migrate a WASCE 2.1.1.5 application to WASCE 3.0; I can deploy it to WASCE 3 but it does not unpack the WAR in the deployment directory like it does in 2.1. I checked the server.xml file and it has the Host attribute unpackWARs="true" but the deployed web app is deployed as a ".car" file.

I tried to do this manually by undeploying the app, unpacking the EAR and WAR to a directory outside of WASCE, and then running the deploy from the command line using --inPlace. It still packages it up in the car again though, not at all what I want.

Is there a way to force WASCE 3 to unpack the WAR like it does by default in WASCE 2.1? This is important for the web app to work as there is some file IO done within the app that doesn't work in WASCE 3 because the directories don't exist when the WAR is packed.