tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabrice Terrasson <...@wanadoo-sp.net>
Subject Re: about TOMCAT+APACHE+SOAP path problem
Date Tue, 28 Aug 2001 21:53:43 GMT
When launching Tomcat as standalone, soap examples works fine.
But with apache I got the error sended earlier.

The context seems to be well formed.


Pae Choi a écrit :
> 
> Have you configured the Apache WS with TOMCAT AS by using the mod_jk,
> unless you are using the CATALINA?
> 
> If so, follow the SOAP installation instruction and configure the SOAP into
> the TOMCAT by adding *new* context almost same as you are adding new
> context to the TOMCAT. So, the Apache will forward the requests that needs
> to be handled by the TOMCAT. And the TOMCAT will know which service
> provider, e.g., SOAP, need to handle the *CONTEXT*, e.g., <whatever>/soap,
> associated requests.
> 
> So the normal order of installation should be Apache + TOMCAT + SOAP
> unless you prefer to in other ways.
> 
> Pae
> 
> > I am trying to make work TOMCAT+APACHE+SOAP together:
> >
> > My server is accessed with this URL:
> > http://brazil/soap
> > returns:
> > ---------------------------------------------------------
> > Not Found
> >
> > The requested URL /soap was not found on this server.
> >
> >
> > Apache-AdvancedExtranetServer/1.3.19 Server at brazil Port 80
> > ---------------------------------------------------------
> >
> > But http://brazil/soap/
> > returns:
> > ---------------------------------------------------------
> > Index of /soap
> >
> >     Name                    Last modified       Size  Description
> >
> >
> >     Parent Directory        18-Aug-2000 13:23      -
> >     WEB-INF/                18-Aug-2000 13:23      -
> >     admin/                  18-Aug-2000 13:23      -
> >     index.html              18-Aug-2000 13:23     1k
> >
> >
> > Apache-AdvancedExtranetServer/1.3.19 Server at brazil Port 80
> > ---------------------------------------------------------
> >
> > Is it about a <Directory> directive trick of Apache ? Anyone got a clue
> > ?
-- 
Cordialement,
Fabrice Terrasson,

Mime
View raw message