Dear Tim and Heiko,

I tested a few things under mvn jetty:run...:

  getRealPath gives me "...../src/main/webapp"
  the temp attribute is set to "...../target/work"
  and the location is "...../target/classes"

While the war contains "classes/work" which is again different...   I
didn't manage to get jetty to serve contents from any other directory
than the first one.

Didn't try to run it on the standalone jetty, since I still don't know
how
to tell jetty to serve contents that is not under the webapp
directory.
Probably have to do something with the site map which I don't fully
understand.

Guess my main problem is that I don't have any experience in this
field (jetty/lift) and thought it wouldn't be to difficult to port my
website
to lift and enhance it a little on the fly.

To be continued...

Job Honig




On Nov 28, 12:52 am, Timothy Perrett <[email protected]> wrote:
> Here's a nugget of information for you that will help (as I do something 
> similar to what you want in one of my applications):
>
>   val protectionDomain: ProtectionDomain = 
> classOf[bootstrap.liftweb.Boot].getProtectionDomain()
>   val location: URL = protectionDomain.getCodeSource().getLocation()
>
> Print the value of location, and that will get you headed in the right 
> direction ;-) Moreover, if your using jetty, if there is a "work" directory 
> next to where the war file is, jetty will automatically expand the war into 
> that work folder... if not, it makes a temp directory in the relevant OS temp 
> directory (/var/tmp on *nix OS)
>
> Godspeed.
>
> Tim.
>
> On 27 Nov 2009, at 21:49, Heiko Seeberger wrote:
>
> > 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]>
> > > > .
> > > > 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 
> > athttp://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 
> > athttp://groups.google.com/group/liftweb?hl=en.

--

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.


Reply via email to