On Sun, Aug 1, 2010 at 5:08 AM, pkcinna <pkci...@gmail.com> wrote: > > There used to be a workaround for Godaddy shared hosting and Wicket but I > cannot find it with Google anymore. > > Any suggestions for the following Godaddy shared hosting restrictions? > > 1) Cannot write to file system except /tmp directory. Does wicket attempt > to open any files in write mode on startup?
use session store to store the pages, then no files will be created. > 2) Tomcat restarted at 1am Arizona time daily. How will this effect users > if they have a session open at that time? Will the session be lost with > wicket or will it persist okay? only if tomcat is configured to persist them across restarts > 3) filters don't seem to work and app context root can't be "/" since its on > a shared tomcat process. How can I setup wicket to run as a servlet? see WicketServlet -igor > > I am hoping if I use a org.apache.log4j.jdbc.JDBCAppender with log4j it will > actually show stack traces of what goes wrong. Very painful process but > this is the environment I'm stuck with. > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Godaddy-shared-hosting-workaround-tp2309403p2309403.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
