--- "Broderick, Andrew" <[EMAIL PROTECTED]> wrote:
> Deploying as an exploded .war worked. Some Googling showed that others
> have had the same problem deploying as a packaged .war, because Roller
> tries to access config files using ServletContext.getRealPath(), which
> returns null unless it is a directory rather than a packaged .war file.
>
> If anyone reading this encounters the same problem, it IS possible to
> deploy on WebLogic as an exploded .war. Just unzip the .war to a
> directory on your server and navigate to it using the console - it will
> detect that the directory is in fact a web application and allow you to
> deploy it.
>
Actually I came to the conclusion (despite my original postings!) that the
getRealPath() returning
null wasn't really a problem as all of its calls I could find in the source
were overridden by the
following settings in roller-custom.properties:
uploads.dir=/somepath/roller-data/resources
themes.dir=/somepath/roller-data/themes
search.index.dir=/somepath/roller-data/search-index
I haven't tried this on WLS but on OC4J, if you set the above paths, Roller
runs quite happily
from the (unexploded) .war file.
>From reading the comments in the source code I think the intention is that,
>from Roller 4, themes
and uploads would ideally be outside of the context root anyway, so that when
you redeploy you
don't lose them.
Therefore my suggestion would be after you've unzipped the Roller 4 download,
you create a
roller-data directory somewhere else and move the themes directory into there
(plus create a
couple of empty directories for uploads and search-index). Then create the war
file, create the
roller-custom.properties somewhere on the container classpath and then deploy.
Simon
__________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
