axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepak Bhole (JIRA)" <>
Subject [jira] Commented: (AXIS2-441) Axis 0.94 - Can't use other urlpath than /services/*. Gives "AxisService Not found yet" in the reply as an AxisFault.
Date Fri, 10 Feb 2006 20:57:14 GMT
    [ ] 

Deepak Bhole commented on AXIS2-441:

It doesn't seem like the service folder is meant to be configurable (from the axis perspective).
The "services" directory is hardcoded. AFAIK, the web.xml is used only by tomcat for figuring
out which servlet to send the request to.

> Axis 0.94 - Can't use other urlpath than /services/*. Gives "AxisService Not found yet"
in the reply as an AxisFault.
> ---------------------------------------------------------------------------------------------------------------------
>          Key: AXIS2-441
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Versions: 0.94
>  Environment: Windows XP, Tomcat 5.5.7, j2sdk 1.4.2_08, axis 0.94.
>     Reporter: Anders Syvertsen

> Trying to run axis2 under a different urlpath than the default, /services/* but it doesnt
> Changing in web.xml the default mapping to,
> <servlet-mapping>
>     <servlet-name>Axis2Servlet</servlet-name>
>     <url-pattern>/services2/*</url-pattern>
> </servlet-mapping>
> and it crashes when i try to invoke the service, when pointing my browser to the WSDL
it displays correctly though.
> The stacktrace axis2 replies with is:
> <?xml version="1.0" encoding="UTF-8" ?>
> <soapenv:Envelope xmlns:soapenv="">
> 	<soapenv:Header />
> 	<soapenv:Body>
> 		<soapenv:Fault>
> 			<faultcode>Client</faultcode>
> 			<faultstring>AxisService Not found yet</faultstring>
> 			<faultactor>http://myAxisServer/role/default</faultactor>
> 			<detail>
> <soapenv:Exception>org.apache.axis2.AxisFault: AxisService Not found yet at org.apache.axis2.engine.InstanceDispatcher.fillContextsFromSessionContext(
at org.apache.axis2.engine.InstanceDispatcher.invoke( at org.apache.axis2.engine.Phase.invoke(
at org.apache.axis2.engine.AxisEngine.invoke( at org.apache.axis2.engine.AxisEngine.receive(
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
at org.apache.axis2.transport.http.AxisServlet.doPost( at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service( at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
at org.apache.catalina.core.StandardWrapperValve.invoke( at
org.apache.catalina.core.StandardContextValve.invoke( at org.apache.catalina.core.StandardHostValve.invoke(
at org.apache.catalina.valves.ErrorReportValve.invoke( at org.apache.catalina.core.StandardEngineValve.invoke(
at org.apache.catalina.connector.CoyoteAdapter.service( at org.apache.jk.server.JkCoyoteHandler.invoke(
at org.apache.jk.common.HandlerRequest.invoke( at org.apache.jk.common.ChannelSocket.invoke(
at org.apache.jk.common.ChannelSocket.processConnection( at org.apache.jk.common.SocketConnection.runIt(
at org.apache.tomcat.util.threads.ThreadPool$ at</soapenv:Exception>
> 			</detail>
> 		</soapenv:Fault>
> 	</soapenv:Body>
> </soapenv:Envelope>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message