I gave two things a shot and they both don't work.
1) I changed my context root of my Wicket application to /xyz (instead of
the default /) and I put an index.html file in my root that looks like this:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
titleXYZ/title
meta
there is always the wicket servlet you can use instead of the filter.
-igor
On Mon, Nov 17, 2008 at 5:41 AM, moraleslos [EMAIL PROTECTED] wrote:
I gave two things a shot and they both don't work.
1) I changed my context root of my Wicket application to /xyz (instead of
the default /) and I
Hi,
Thanks for the reply. I did a quick check and would assume that Tomcat 5.0
supported 2.4 since the description on Apache's Web site says Apache Tomcat
5.5.x supports the same Servlet and JSP Specification versions as Apache
Tomcat 5.0.x., which happens to be Servlet 2.4 / JSP 2.0 (
It was just a guess!
-Ursprüngliche Nachricht-
Von: moraleslos [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 16. November 2008 17:37
An: users@wicket.apache.org
Betreff: RE: Unable to load Wicket app in hosting provider
Hi,
Thanks for the reply. I did a quick check and would assume
BTW, I did test this on my box using Tomcat 5.0.27 with that same v2.4
deployment descriptor and the wicket filters and it worked fine. Not sure
if one can enforce Tomcat 5.0.27 to use 2.3 instead of 2.4.
-los
--
View this message in context:
sounds like a rights problem on godaddy's part. Either they need to do
some tweaking of their apache side (I assume they have apache httpd
running in front of tomcat) or something else is fishy. this does not
sound like a Wicket problem.
Did you try deploying a helloworld servlet?
Martijn
On
Thanks for the reply. I think it could be a rights problem since a 403 error
is typically a permissions issue but I'm not sure how to explain it to these
GoDaddy people because they're really inexperienced. If this is an apache
issue, what are the things I need to look for in order for me to
Didn't try GoDaddy but left 3 other hostings because Wicket did not work there.
On one it didn't work at all.
On two others app opened 1-2 times and then hanged down for unknown time.
Now I opened an account on javaprovider.net - Private JVM Developer.
Wicket works here and I'm glad BUT works
Maybe this helps. I've found that you need to start Tomcat from a
directory that is writable for the user you are using (no idea why
though). Besides the application log, you should also check Tomcat's log
files.
Good luck,
Erik.
moraleslos wrote:
Hi,
I'm running into an issue where my
Ok,
Finally talked to someone at GoDaddy who gave me some advice. With their
Java hosting, it seems that they force Tomcat to look for a default file
(e.g. index.html) at the root directory. Since I don't have one (all of my
files are under WEB-INF/classes/...), I get the 403 error.
Now
mount the wicket filter under context root app and tell the index.html
to redirect to that url with a pragma header.
Martijn
On Mon, Nov 17, 2008 at 1:10 AM, moraleslos [EMAIL PROTECTED] wrote:
Ok,
Finally talked to someone at GoDaddy who gave me some advice. With their
Java hosting, it
Hi '
If I were you I would pick up the wicket in action book, or follow a
tutorial... These are very basic questions...
Wicket has a application class which specify the home folder with a
method, you would override that and return your index.class wicket will
then use that to display as
you just need a file named index.html in your /xyz dir
-igor
On Sun, Nov 16, 2008 at 5:01 PM, moraleslos [EMAIL PROTECTED] wrote:
Hi,
Thanks for the reply. I'm a bit confused on how to write the index.html.
So, let's say my godaddy directory structure looks like this:
/
/xyz
13 matches
Mail list logo
