On 2/8/07, Aaron Mulder <[EMAIL PROTECTED]> wrote:
You can look at var/config/config.xml, and see if there's an entry in there for the application. If so you could remove it
Found one; did that, problem still happened.
or add load="false", but it sounds like maybe there's not an entry? You can also find the files for the application in geronimo/repository (in a subdirectory based on the application's module ID) and delete them. That will make sure there's nothing "blocking" the new deployment.
Will try that next time, thanks. Actually now that you mention it I believe I've tried that previously in addition to editing config.xml, and it solved the problem, but I had forgotten.
