subject:"RE\: Unable to load Wicket app in hosting provider"

Re: Unable to load Wicket app in hosting provider

2008-11-17 Thread moraleslos


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 http-equiv=Refresh content=0;URL=http://www.xyz.com/xyz;
/head
/html

The site reads my index.html properly and redirects, but redirects to a 404
error page.

2) I uploaded the entire wicket_in_action_0.9 war file under the context
root /wicket_in_action.  When I type www.xyz.com/wicket_in_action, I get a
404 because it tries to redirect me to www.xyz.com/wicket_in_action/app
(which is correct since the default index.html file uses the same refresh
technique but to /app which does not exist).  Now if I type in this
directly: http://www.xyz.com/wicket_in_action/home, I also get a 404 error.  

From the above, it seems to me that the Java hosting site's Tomcat is not
able to load any Wicket-based app probably due to not being able to
understand and/or load the Wicket filter defined in the web.xml file. 
Regardless if I have a static default page (index.html) that redirects to a
Wicket URL will not work.  

Any other ideas I may try out before giving up?  Thanks!

-los


igor.vaynberg wrote:
 
 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
 /xyz/WEB-INF
 /xyz/WEB-INF/web.xml
 /xyz/WEB-INF/classes/com/xyz/Index.html
 /xyz/WEB-INF/classes/com/xyz/Index.class
 ...

 In my web.xml looks like this:

 web-app
version=2.4
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

display-namexyz/display-name
context-param
param-nameconfiguration/param-name
param-valuedeployment/param-value
/context-param
filter
filter-namewicket.xyz/filter-name
   
 filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name
param-valuecom.xyz.XyzApplication/param-value
/init-param
/filter
filter-mapping
filter-namewicket.xyz/filter-name
url-pattern/*/url-pattern
/filter-mapping
 /web-app


 So how do I write the index.html that's going to be in the root directory
 to
 invoke Wicket's Index.html under /xyz/WEB-INF/classes/com/xyz/Index.html?
 Thanks!

 -los


 Martijn Dashorst wrote:

 so your wicket filter would service all requests going to:

 http://godaddy.com/myapplication/app

 or, you could still keep the filter mapping to /* but redirect to your
 mounted homepage with mount name home or something similar.

 Martijn

 On Mon, Nov 17, 2008 at 1:40 AM, Martijn Dashorst
 [EMAIL PROTECTED] wrote:
 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 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 here's the question.  How do I write up a default index.html file
 and
 place this in the root directory such that it will start up the
 Wicket
 filter in the web.xml file and run the Wicket application
 appropriately?
 Again, my actual Index.html, and hence it's Index.class, is packaged
 under
 the WEB-INF/classes/... directory.  Thanks!

 -los



 Erik van Oosten wrote:

 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 Wicket-based application will
 absolutely
 not load in the shared hosting environment.  I'm trying out
 GoDaddy's
 Java
 Web hosting that uses Java 1.5 and Tomcat 5.0.27.  I have this same
 setup
 on
 my box and deploying my Wicket 1.3.4-based application works

 --
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 --
 View this message in context:

Re: Unable to load Wicket app in hosting provider

2008-11-17 Thread Igor Vaynberg

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 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 http-equiv=Refresh content=0;URL=http://www.xyz.com/xyz;
 /head
 /html

 The site reads my index.html properly and redirects, but redirects to a 404
 error page.

 2) I uploaded the entire wicket_in_action_0.9 war file under the context
 root /wicket_in_action.  When I type www.xyz.com/wicket_in_action, I get a
 404 because it tries to redirect me to www.xyz.com/wicket_in_action/app
 (which is correct since the default index.html file uses the same refresh
 technique but to /app which does not exist).  Now if I type in this
 directly: http://www.xyz.com/wicket_in_action/home, I also get a 404 error.

 From the above, it seems to me that the Java hosting site's Tomcat is not
 able to load any Wicket-based app probably due to not being able to
 understand and/or load the Wicket filter defined in the web.xml file.
 Regardless if I have a static default page (index.html) that redirects to a
 Wicket URL will not work.

 Any other ideas I may try out before giving up?  Thanks!

 -los


 igor.vaynberg wrote:

 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
 /xyz/WEB-INF
 /xyz/WEB-INF/web.xml
 /xyz/WEB-INF/classes/com/xyz/Index.html
 /xyz/WEB-INF/classes/com/xyz/Index.class
 ...

 In my web.xml looks like this:

 web-app
version=2.4
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

display-namexyz/display-name
context-param
param-nameconfiguration/param-name
param-valuedeployment/param-value
/context-param
filter
filter-namewicket.xyz/filter-name

 filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name
param-valuecom.xyz.XyzApplication/param-value
/init-param
/filter
filter-mapping
filter-namewicket.xyz/filter-name
url-pattern/*/url-pattern
/filter-mapping
 /web-app


 So how do I write the index.html that's going to be in the root directory
 to
 invoke Wicket's Index.html under /xyz/WEB-INF/classes/com/xyz/Index.html?
 Thanks!

 -los


 Martijn Dashorst wrote:

 so your wicket filter would service all requests going to:

 http://godaddy.com/myapplication/app

 or, you could still keep the filter mapping to /* but redirect to your
 mounted homepage with mount name home or something similar.

 Martijn

 On Mon, Nov 17, 2008 at 1:40 AM, Martijn Dashorst
 [EMAIL PROTECTED] wrote:
 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 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 here's the question.  How do I write up a default index.html file
 and
 place this in the root directory such that it will start up the
 Wicket
 filter in the web.xml file and run the Wicket application
 appropriately?
 Again, my actual Index.html, and hence it's Index.class, is packaged
 under
 the WEB-INF/classes/... directory.  Thanks!

 -los



 Erik van Oosten wrote:

 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 Wicket-based application will
 absolutely
 not load in the shared hosting environment.  I'm trying out
 GoDaddy's
 Java
 Web hosting that uses Java 1.5 and Tomcat 5.0.27.  I have this same
 setup
 on
 my box and deploying my Wicket 1.3.4-based application works

 --
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For

RE: Unable to load Wicket app in hosting provider

2008-11-16 Thread moraleslos

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 (
http://tomcat.apache.org/whichversion.html
http://tomcat.apache.org/whichversion.html ).

Lets say that Tomcat 5.0 only supports 2.3. Another check on the 2.3 dtd
shows that it doesn't have servlet filters. If this is the case, how do I
define Wicket in the deployment descriptor without having to use Wicket
filters? Is there a Wicket servlet I can configure? Thanks.

-los

Stefan Lindner wrote:

I guess that 'web-app version=2.4' means this is a web application for
servlet version 2.4. But Tomcat 5.0 supports only version 2.3? Mybe this
could help you. Or you just drop the 'version =...' attribute.

Stefan

-Ursprüngliche Nachricht-
Von: moraleslos [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 16. November 2008 16:36
An: users@wicket.apache.org
Betreff: Unable to load Wicket app in hosting provider

Hi,

I'm running into an issue where my Wicket-based application will
absolutely
not load in the shared hosting environment. I'm trying out GoDaddy's Java
Web hosting that uses Java 1.5 and Tomcat 5.0.27. I have this same setup
on
my box and deploying my Wicket 1.3.4-based application works. However,
deploying the exact same war file on GoDaddy will not work. The war
explodes appropriately but it seems as though Tomcat doesn't know what to
do
with it. I always get a 403 error when accessing my site. The
application
is really simple-- no DB even. I made sure that log4j wrote to their /tmp
directory to avoid any issues. I contacted GoDaddy and they said they
could
not find any issues on their side.

Although I probably won't continue with Godaddy after my month is up, I
just
can't seem to debug this issue. Its a really simple Wicket app that
should
work on any hosting environment. All of my files are under the
directories:
/WEB-INF/classes/
/WEB-INF/lib/
/WEB-INF/web.xml

My deployment descriptor looks like this:

web-app
version=2.4
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

display-namemoralesTest/display-name
context-param
param-nameconfiguration/param-name
param-valuedeployment/param-value
/context-param
filter
filter-namewicket.moraleslos/filter-name

filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name

param-valuecom.moraleslos.WicketTestApplication/param-value
/init-param
/filter
filter-mapping
filter-namewicket.moraleslos/filter-name
url-pattern/*/url-pattern
/filter-mapping
/web-app

Again, it seems as though Tomcat doesn't understand Wicket filters or
something, since I always get a 403 error. Any ideas on how I should debug
and/or fix this issue would be appreciated. Thanks.

-los
--
View this message in context:
http://www.nabble.com/Unable-to-load-Wicket-app-in-hosting-provider-tp20526412p20526412.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
View this message in context:
http://www.nabble.com/Unable-to-load-Wicket-app-in-hosting-provider-tp20526412p20527093.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Unable to load Wicket app in hosting provider

2008-11-16 Thread Stefan Lindner

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