I guess this is something new in SOAP 2.2
I will look into it.
thanks,
shinta
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 08, 2001 10:05 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: ConfigManager 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 Corporate Campus Drive,
> Suite 2000
> Louisville, KY 40223
>
>
>
>
> "Shinta Tjio"
>
> <stjio@broadj To:
> <[EMAIL PROTECTED]>
>
> ump.com> cc:
>
> Subject: RE:
> ConfigManager can not read DeployedServices.ds
>
> 06/08/01
>
> 10:50 AM
>
> Please
>
> respond to
>
> soap-user
>
>
>
>
>
>
>
>
>
> Understood. And it seems like Sun just completely punt this
> problem (I can't find any documentation that suggest
> a workaround).
>
> This has made out migration a bit tricky. Redeploying the
> services could be hard because those deployed services
> could be modified on the field (via the Admin GUI) and
> we certainly don't want our customers to re-enter their
> changes.
>
> It seems to me Java serialization is not a good choice,
> if you seriously thinking about providing some kind of
> backwards compatibility.
>
> Any thoughts from the SOAP dev people?
>
> -shinta
>
> > -----Original Message-----
> > 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 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 simply redeploy your services using
> > your current
> > JVM and all should be well again.
> >
> > Mike
> >
> > Shinta Tjio wrote:
> >
> > > 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:
> > >
> > > java org.apache.soap.server.ServiceManagerClient
> > > http://brian:48080/soap/servlet/rpcrouter list
> > >
> > > SOAP Service Manager: Unable to read
> 'DeployedServices.ds': assuming
> > > fresh start
> > > java.io.InvalidClassException:
> > > org.apache.soap.server.DeploymentDescriptor;
> > > Local class not compatible: stream classdesc
> > > serialVersionUID=2926881600043336890
> > > local class serialVersionUID=-1581712267782747801
> > >
> > > Did anyone see this kind of error? Other than
> > > reverting back to JDK 1.2.2_05a, anyone has any
> > > suggestion on how to handle this?
> > >
> > > thanks,
> > > shinta
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> >
> >
> > --
> >
> >
> > ----------------------------
> > Mike Williams
> > [EMAIL PROTECTED]
> > http://www.mikesbox.com
> > ----------------------------
> > May the Source be with you!
> > ----------------------------
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
