I am sure that it is tomcat that I am speaking to.  I still get gibberish
when I try http://localhost:port or http://localhost:port/soap.

---------------------------------------------------------------------
Rich Catlett        [EMAIL PROTECTED] |  Confuscious say "Man who stand |
Programmer                        |   on toilet, high on pot!"      |
                                  |                                 |
---------------------------------------------------------------------

On Thu, 21 Jun 2001, Matthew J. Duftler wrote:

> Hi Rich,
> 
> What happens if you just put in:
> 
> http://localhost:port
> 
> or
> 
> http://localhost:port/soap
> 
> Do you still get the gibberish? Are you sure it is Tomcat you're speaking
> to, and not some other server running?
> 
> Thanks,
> -Matt
> 
> > -----Original Message-----
> > From: Rich Catlett [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, June 20, 2001 5:59 PM
> > To: [EMAIL PROTECTED]
> > Subject: new to soap
> >
> >
> > I just set up soap running on tomcat 4, and I can't get it to work.  When
> > I go to http://localhost:port/soap/servlet/rpcrouter (yes I have put in a
> > number for port) I get gibberish everytime I reload the page I get
> > something different like the following
> > me+
> > )??
> > Dl)
> > so on and so forth.  One problem that I know tomcat currently has is that
> > it is not able to find servlets unless they are in the top level of the
> > classes directory.  If they are in a jar file of a package they are not
> > found.  I did note that even before I changed this I was still getting the
> > gibberish and not a resource unavailable, I think it's a 404 error.  I was
> > wondering if anyone had run across this problem or had any ideas about
> > fixing it.  Thanks.
> >
> > ---------------------------------------------------------------------
> > Rich Catlett        [EMAIL PROTECTED] |  Confuscious say "Man who stand |
> > Programmer                        |   on toilet, high on pot!"      |
> >                                   |                                 |
> > ---------------------------------------------------------------------
> >
> 
> 

Reply via email to