Problems with isWarDeployed

[cjh]

For various reasons, we don't deploy our application as a war file on
tomcat, but simply as a directory tree, with the appropriate tomcat
XML settings.

The easiest way to create those directories, though, is to run "grails
war" and then unzip the resulting .war file.

The problem is that Autobase is checking the isWarDeployed property of
the application, which is apparently set to true when you run the war
command, and subsequently failing to initialize since it's looking for
changelog.groovy on the classpath.

Is there any way I can override Autobase's logic so that it always
uses the file loader rather than classpath loader when getting
changelog.groovy and *Migration.groovy?

Thanks,
Chris

--
Chris Hoffmann/Center for Educational Software Development
UMass Amherst/x51555

[Robert Fischer]

Hrm. There isn't a way do to this right now. How would you like it to be signaled?

~~ Robert.

--
~~ Robert Fischer.
Grails Trainining http://www.smokejumperit.com/grails_training.html
Smokejumper Consulting http://smokejumperit.com
Enfranchised Mind Blog http://enfranchisedmind.com/blog

[cjh]

Robert,

What I was thinking of doing as a local patch was modifying all the
places that are looking at isWarDeployed() and also look for a
configuiration parameter, say "autobase.warfiledeployed" and see if it
is false. If its false, then use the file loader.

Chris

On Dec 31 2008, 9:34 am, Robert Fischer

[Robert Fischer]

That'd work for you. It doesn't work for a general solution -- I'm trying to figure out how to
implement an override that will work well.

~~ Robert.