Job, This directory is managed by the servlet container and as far as I know there is little you can do to configure the location. If you use Tomcat you are able to specify CATALINA_BASE and it will be somewhere beneath that directory, I believe it is work/Catalina/localhost/<WABAPP-NAME>.
Regarding serving images from there: Depending on the configuration of the servlet container WARs are not unpacked, hence there is no standard way to bring these images "into" your webapp. I think you will not be able to have the servlet container serve these images directly. But it should be easy to write a ServletFilter or something that will do it for you. Heiko 2009/11/27 jhonig <[email protected]> > Heiko, > > In the meantime, I found that solution as well... I tried it, and > the default seems to > be a "work" directory in "target". I guess I can set another value > for the attribute > if I manage to convince jetty to do that for me. What I forgot to > mention is that > the directory is to contain images that are to be served by jetty... > So it means > the directory should be logically under webapp, but not in the war (of > course). > > If I use a link from inside the war to some regular file system > location, I'll > probably run into the same problem as before. Any idea how to do > this? > > Job H. > > On Nov 27, 6:56 pm, Heiko Seeberger <[email protected]> > wrote: > > File tempdir = (File) > > config.getServletContext().getAttribute("javax.servlet.context.tempdir") > > > > 2009/11/27 jhonig <[email protected]> > > > > > > > > > Dear Heiko, > > > > > > According to the Servlet spec each webapp has got a private temporary > > > > directory. I cannot remember exactly how to get this, maybe > > > > ServletContext.getTmpDir(). Please take a look at the spec. > > > > > I started reading the spec, but didn't find it yet. ServletContext > > > doesn't > > > have any obvious way to get to a temporary dir, but I assumed I could > > > create one. Would probably need to tweak a security policy to be able > > > to write to it, but that would be the next step. > > > > > Job H. > > > > > -- > > > > > You received this message because you are subscribed to the Google > Groups > > > "Lift" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<liftweb%[email protected]> > <liftweb%[email protected]<liftweb%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/liftweb?hl=en. > > > > -- > > Heiko Seeberger > > > > My job: weiglewilczek.com > > My blog: heikoseeberger.name > > Follow me: twitter.com/hseeberger > > OSGi on Scala: scalamodules.org > > Lift, the simply functional web framework: liftweb.net > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > > -- Heiko Seeberger My job: weiglewilczek.com My blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
