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?
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?
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?

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:
Sent from the Wicket - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to