sure, but I would be almost 99% sure that if the WAR file isn't causing 
problems it's because at deployment time you are unpackaging the WAR and 
running the app from that.

on tomcat the app won't run from an unpackaged WAR file.

-- Allen


On Thu, 2005-11-17 at 14:44, Elias Torres wrote:
> We have an ANT task that builds a WebSphere specific WAR. I can ask
> the intern who did that to share it.
> 
> Elias
> 
> On 11/17/05, Allen Gilliland <[EMAIL PROTECTED]> wrote:
> > oops, found another reason ...
> >
> > javax.servlet.ServletException: Error initializing Velocity: 
> > java.io.FileNotFoundException: /WEB-INF/velocity.properties (No such file 
> > or directory)
> >         
> > org.apache.velocity.servlet.VelocityServlet.initVelocity(VelocityServlet.java:197)
> >         
> > org.apache.velocity.servlet.VelocityServlet.init(VelocityServlet.java:162)
> >         
> > org.roller.presentation.velocity.BasePageServlet.init(BasePageServlet.java:52)
> >
> > looks like the VelocityServlet tries to read the velocity properties via a 
> > FileInputStream :(
> >
> > -- Allen
> >
> >
> > On Thu, 2005-11-17 at 11:33, Allen Gilliland wrote:
> > > What are our current obstacles which are keeping us from packaging as a 
> > > WAR file?  Particularly a non-exploding WAR file.
> > >
> > > I have ...
> > >
> > > 1. we still allow some older users to write resources inside the webapp, 
> > > so we need access to the context path.  this can probably be removed 
> > > pretty soon and we can force everyone to keep their uploads outside the 
> > > webapp.
> > >
> > > 2. we still need the context path for reading theme files.  this is 
> > > tricky, but maybe theme files should be outside the webapp as well?  if 
> > > not, then maybe they should be in the WEB-INF/classes directory so we can 
> > > access them through the classpath?
> > >
> > >
> > > can anyone think of any others?
> > >
> > > not deploying as a WAR is one of my pet peeves with Roller and I think 
> > > it's something we should work on pretty soon.
> > >
> > > -- Allen
> > >
> >
> >

Reply via email to