nable to read 'DeployedServices.ds': assuming fresh
start
The service is deployed properly. Here is the result of list from
ServiceManagerClient.
D:\ProJavaSoap\Chapter03\HelloWorld>java
org.apache.soap.server.ServiceManagerClient
http://localhost:8080/helloworld/rpcrou
To: [EMAIL PROTECTED]
cc:
0
xml:
> >
> >
> >
> >
> >
> >
> > There is probably a similar configuration setup using the .ds file.
> >
> > Shawn.
> >
> >
> >
> > [EMAIL PROTECTED] To: [EMAIL PROTE
efine the location of the deployment descriptor file (dds.xml).
>
> soap.xml:
>
>
>
>
>
>
> There is probably a similar configuration setup using the .ds file.
>
> Shawn.
>
>
>
> [EMAIL PROTECTED] To: [EMAIL PROTECTED]
>
cc:
03/20/2002 11:06 Subject: DeployedServices.ds
Has anyone succesfully been able to specify a different location for the
DeployedServices.ds file. I have tried a few times and it always seems
like the servlet never picks up any of the changes that I make to the
deployment descriptor. If anyone as any suggestions I would appreciate
it.
Thanks
Title: How do give the path for the Deployment Descriptor file [DeployedServices.ds]
Hi,
I have Tomcat 4.x with Apache Soap 2.2. Using the web browser admin-interface, I have deployed some services.
The deployed services are stored in the $(Catalina_home)\DeployedServices.ds file.
Q
I've sorted out my classpath and everything has sorted it out.
please ignore the question.
cheers
Chris Seldon
'DeployedServices.ds': assuming fresh
start
I would have expected the browser screen to show me a message or an empty
list.
Similarly the Deploy/Undeploy options do not work, and display a similar
pattern.
Could someone please inform me how I can create a DeployedServices.ds file
or where I can find on
/lang/ClassLoader;)Ljava/lang/Class; not
found
On the server side, here's the message that Tomcat gave:
SOAP Service Manager: Unable to read 'DeployedServices.ds': assuming
fresh start
Is 'DeployedServices.ds' a standard file? Where is it? (None of the
folders seemed to have any
the error?
>
> Thanks,
> -Matt
>
> > -Original Message-
> > From: Rahul Kirthivasan
> [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, June 08, 2001 5:57 AM
> > To: [EMAIL PROTECTED]
> > Subject: DeployedServices.ds - IS there a way to
> forcibly remo
nager can not read DeployedServices.ds
>
>
>
> Soap offers an XML version of the DeployedServices.ds. Have
> you looked
> into it?
>
> James Birchfield
>
> Ironmax
> maximizing your construction equipment assets
> 5 Corporate Center
> 9960 Co
persistence mechanism of
their choice.
Thanks,
-Matt
> -Original Message-
> From: Shinta Tjio [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 08, 2001 10:50 AM
> To: [EMAIL PROTECTED]
> Subject: RE: ConfigManager can not read DeployedServices.ds
>
>
> Understood. An
Soap offers an XML version of the DeployedServices.ds. Have you looked
into it?
James Birchfield
Ironmax
maximizing your construction equipment assets
5 Corporate Center
9960 Corporate Campus Drive,
Suite 2000
Louisville, KY 40223
> From: Mike Williams [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 06, 2001 5:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ConfigManager can not read DeployedServices.ds
>
>
> Shinta,
>
> The problem is with serialization. A class that is
> serialized can on
Hi Rahul,
And what was the error?
Thanks,
-Matt
> -Original Message-
> From: Rahul Kirthivasan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 08, 2001 5:57 AM
> To: [EMAIL PROTECTED]
> Subject: DeployedServices.ds - IS there a way to forcibly remove a
> Webservic
Hi all,
I am trying to remove a deployed service using
the SOAP Admin tool. But I get an error. Is there
a way to forcibly remove it. I guess the details
are written into DeployedServices.ds
Is there a way to forcibly delete a service
to prevent it from appearing in the
SOAP Admin tool
Shinta,
The problem is with serialization. A class that is serialized can only
be deserialized with the same version of the JVM. The
DeployedServices.ds file is a serialized hash map or maps of
DeploymentDescriptors. This is what's causing your problem.
You should be able to s
We have an installation where the first few
SOAP services were deployed using JDK 1.2.2_05a
for Solaris 2.8. Later on, the JVM on that machine
is upgraded to JDK 1.2.2_06. I'm finding that the
ConfigManager could not read the DeployedServices.ds.
This is the exception thrown:
19 matches
Mail list logo
