I see that DeployedServices.ds seems to sit in the /soap webapp directory. Maybe this relates to my problem. The example I'm following from the SOAP book I'm using suggests that it's ideal to deploy your SOAP service in its own context, rather than in the /soap context. So I created a new context called /hello which has a web.xml as follows:
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<display-name>Hello World Sample</display-name>
<description>This is Hello World Service.</description>
<servlet>
<servlet-name>Apache-SOAP RPC Router</servlet-name>
<display-name>Apache-SOAP RPC Router</display-name>
<description>The Apache-SOAP RPC Router.</description>
<servlet-class>
org.apache.soap.server.http.RPCRouterServlet
</servlet-class>
<init-param>
<param-name>faultListener</param-name>
<param-value>org.apache.soap.server.DOMFaultListener</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>Apache-SOAP Message Router</servlet-name>
<display-name>Apache-SOAP Message Router</display-name>
<servlet-class>org.apache.soap.server.http.MessageRouterServlet</servlet-class>
<init-param>
<param-name>faultListener</param-name>
<param-value>org.apache.soap.server.DOMFaultListener</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>Apache-SOAP RPC Router</servlet-name>
<url-pattern>/rpcrouter</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Apache-SOAP Message Router</servlet-name>
<url-pattern>/messagerouter</url-pattern>
</servlet-mapping>
</web-app>
This exposes the SOAP RPC router through my new context. I assume this is good practice, since you don't want all your SOAP apps accessible from a single context. But based on this, I believe my command line to list deploys should be like this:
java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/hello/rpcrouter list
In other words, I assume each SOAP context with its own RPC router has its own DeployedServices.ds. Is that how it works? Or are the deployments global?
Jason
On Wednesday, May 29, 2002, at 01:45 PM, Erich Izdepski wrote:
Jason-
DeployedServices.ds is a record of the services you have deployed. It is
read at startup so that you do not have to re-deploy your services when
tomcat is restarted. A fresh start means you have no services deployed. Try
to list them using this from the command line:
java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/rpcrouter list
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: Re: SOAP client access problem
Biju,
Thanks for the suggestion. Unfortunately, the URNs are both lowercase
and identical.
I discovered something else may be relevant to the problem... when I
restart Tomcat, I see this sometimes appearing in my catalina.out:
SOAP Service Manager: Unable to read 'DeployedServices.ds': assuming
fresh start
Is this normal? If not, what does it signify?
Thanks,
Jason
On Wednesday, May 29, 2002, at 01:17 PM, Biju Raman wrote:
Hi
the uri identification is case sensitive . so may be you must have
misspelled
the urn identifier or the letter case may be incorrect.
please check whether the deployed service uri and the one on the client
program are the same.
regards
biju
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: <mailto:[EMAIL PROTECTED]>
list-unsubscribe: <mailto:[EMAIL PROTECTED]>
list-post: <mailto:[EMAIL PROTECTED]>
Delivered-To: mailing list [EMAIL PROTECTED]
Date: Wed, 29 May 2002 12:00:22 -0700
Mime-Version: 1.0 (Apple Message framework v481)
Subject: SOAP client access problem
From: Jason Wells <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Transfer-Encoding: 7bit
X-Loop-Detect: 1
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
Hello,
As someone very new to SOAP, I'm trying to get a very simple SOAP
client
I wrote to talk to a simple SOAP service that I've deployed. I'm
running
into a problem.
The service is deployed under "urn:helloworld", and when I look at the
deployed service information in the Apache SOAP admin app, everyting
appears to be in order. However, When I run the client, I get a fault
string "service 'urn:helloworld' unknown".
Are there any typical reasons why an URN listed in the admin app
wouldn't be accessible by a SOAP client?
Thanks,
Jason
