jhonig <[email protected]> writes: > 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.
I think you need to figure out how your URLs map to resources in 1) your app and 2) the tmp files you generate. If the files in 2) is outside your app context, you configure jetty to serve the files like this http://docs.codehaus.org/display/JETTY/Static+Content If the files in 2) is inside your app context, you need to make your Lift app handle the urls with sitemap and some code that can send the correct files based on the urls. I think these are the only two options if you are not using a frontend such as nginx (highly recommended). If you do use a frontend, you can configure all kind of url mappings there.... So perhaps a few more details on the required mappings could help... /Jeppe -- 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.
