Thanks!
Maybe this should be highlited on the Hello World example on the sourceforge page? It's where most people will start and you will have countless newbies hitting their heads on the wall wondering what happens - or whats not happening.

On 4/23/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
just look at how the quickstart project does this:
By having a index.html in the root:


<html>
<head>
    <meta http-equiv="Refresh" content="0; url=""
</head>
</html>

and you have a servlet mapping of helloworld so:


<html>
<head>
    <meta http-equiv="Refresh" content="0; url=""></head>
</html>


johan


On 4/23/06, Rui Pacheco < [EMAIL PROTECTED]> wrote:
This one did it. This was it, the context. Thank you very much for the tip and for everyone's help and hints.

But if I say that my index page is helloworld, hitting http://localhost:8080/helloworld/ should produce the same as http://localhost:8080/helloworld/helloworld, as the request would be automatically redirected to the default page, no?

Please correct me if I'm wrong. Of course, a better thing to give me instead of an explanation would be a link for me to read ;)


On 4/23/06, Johan Compagner < [EMAIL PROTECTED]> wrote:
so you don't have youre helloworld app in a context? The wicket application you deploy is the root context of tomcat?
else if it is the helloworld context you have to do this:


http://localhost:8080/helloworld/helloworld

to hit the wicket servlet.

johan



On 4/23/06, Rui Pacheco <[EMAIL PROTECTED] > wrote:
Hi Gwyn

I've just installed Jetty 5.1 and tried the application with it, and still nothing.

When the server goes up I can see the System.err message on the logs, but nothing more beyond that. Going to http://localhost:8080/helloworld/ returns a 404 and no activity on the server.

This is a big disappointment. My plan was to use Wicket as a replacement for our PHP applications as it has a minimum learning curve and you don't spend your days editing XML files. But on the other hand I can't debug this forever. Oh well, I guess I can say I tried.


On 4/22/06, Gwyn Evans < [EMAIL PROTECTED]> wrote:
Get rid of the

        public Session newSession() {
                // TODO Auto-generated method stub
                return null;
        }

in HelloWorldApplication.java, as with 1.2 at least, that causes a NPE
in the WebApplication class.

On a more general note, I wonder if you switched to testing with Jetty
or Resin, if you'd get a more useful error msg - You might consider
giving it a try using this as a test case.

/Gwyn

On 22/04/06, Rui Pacheco <[EMAIL PROTECTED]> wrote:
> Hi all
>
> Yesterday I sent a message asking wondering why my helloworld application
> didn't go beyond loading the main class by Tomcat. Someone asked for my
> source code, I'm sending it in attachment.
> As I said before, I inserted a System.err on the constructor of the class
> that extends WebApplication and I can see that message on catalina.out. But
> when I go to my browser I can't see anything, I just get a 404. I am using
> Java 5 with Tomcat 5.5.16 and wicket 1.2 rc2 on Linux.
>
> This is really strange, as I don't get any errors on my logs, just the 404.
> --
> Cumprimentos,
> Rui Pacheco
>


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user



--
Cumprimentos,
Rui Pacheco




--
Cumprimentos,
Rui Pacheco




--
Cumprimentos,
Rui Pacheco

Reply via email to