If you are modifying web.xml, doing it via <env-entry/> and having it available via JNDI (java:comp/env) [1] seems closest. However, I am not sure that would be available via System.getProperty ().
Alternately, try jetty.xml (or jetty-env.xml, if possible) [2][3] to do something like: <Call class="java.lang.System" name="setProperty"> <Arg>run.mode</Arg> <Arg>production</Arg> </Call> [1]: http://docs.codehaus.org/display/JETTY/JNDI#JNDI-enventry [2]: http://docs.codehaus.org/display/JETTY/Syntax+Reference [3]: http://docs.codehaus.org/display/JETTY/jetty-env.xml On Sep 13, 1:47 pm, george <geo...@mattandgeorge.com> wrote: > Thanks Xavi > > > I believe you can also modify web.xml in some way, but I'm not really sure. > > that would be useful as I don't have the ability to set properties on > the production environment. > > I wonder if anyone else can confirm? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
