WebServices.BindingBuilder caches

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

WebServices.BindingBuilder caches

Peter Goessaert
Hallo,

In VW 7.2.1 I have a webservice defined in some #wsdlSchema method.
But when I make changes to that wsdl, and reload it via

 WebServices.WsdlBinding loadWsdlBindingFrom: ...

the soap (un)marshaling still uses the formerly loaded wsdl, as if it is
cached somewhere.

Trying to reset WebServices.WsdlBinding and WebServices.WsdlService does
not help, nor does initializing the BindingBuilder.

When I start from a blank image without any webservices code, and then
load my application, everything works as expected following the updated
wsdl.
Sometimes quitting and reopening the image does the trick as well,
sometimes it doesn't - I don't see a pattern there.

Is there a easy way to reset a whole web service at once?

Thank you,

Peter

Reply | Threaded
Open this post in threaded view
|

RE: WebServices.BindingBuilder caches

Kogan, Tamara
In addition to WsdlBinding reset try
"XMLObjectBinding configure" or remove the XML to object binding
(XMLObjectBinding. XMLBindingRegistry) that is related to the wsdl
schema you are updating.

I would suggest upgrading to 7.4.1. There have been quite changes and
bug fixes between 7.2 and 7.4.

Tamara Kogan
Smalltalk development,
Cincom Systems

> -----Original Message-----
> From: Peter Goessaert [mailto:[hidden email]]
> Sent: Tuesday, January 30, 2007 9:13 AM
> To: [hidden email]
> Subject: WebServices.BindingBuilder caches
>
> Hallo,
>
> In VW 7.2.1 I have a webservice defined in some #wsdlSchema method.
> But when I make changes to that wsdl, and reload it via
>
>  WebServices.WsdlBinding loadWsdlBindingFrom: ...
>
> the soap (un)marshaling still uses the formerly loaded wsdl, as if it
is
> cached somewhere.
>
> Trying to reset WebServices.WsdlBinding and WebServices.WsdlService
does
> not help, nor does initializing the BindingBuilder.
>
> When I start from a blank image without any webservices code, and then
> load my application, everything works as expected following the
updated
> wsdl.
> Sometimes quitting and reopening the image does the trick as well,
> sometimes it doesn't - I don't see a pattern there.
>
> Is there a easy way to reset a whole web service at once?
>
> Thank you,
>
> Peter

Reply | Threaded
Open this post in threaded view
|

RE: WebServices.BindingBuilder caches

Steven Kelly
In reply to this post by Peter Goessaert
You probably need to remove the old WSDL first:
 
XMLObjectBinding registry removeKey: myNamespace ifAbsent: [].

We needed to do that, at least in older VW versions. It does no harm in
the latest versions, but may be unnecessary.

HTH,
Steve

> -----Original Message-----
> From: Peter Goessaert [mailto:[hidden email]]
> Sent: 30 January 2007 16:13
> To: [hidden email]
> Subject: WebServices.BindingBuilder caches
>
> Hallo,
>
> In VW 7.2.1 I have a webservice defined in some #wsdlSchema method.
> But when I make changes to that wsdl, and reload it via
>
>  WebServices.WsdlBinding loadWsdlBindingFrom: ...
>
> the soap (un)marshaling still uses the formerly loaded wsdl, as if it
is
> cached somewhere.
>
> Trying to reset WebServices.WsdlBinding and WebServices.WsdlService
does
> not help, nor does initializing the BindingBuilder.
>
> When I start from a blank image without any webservices code, and then
> load my application, everything works as expected following the
updated
> wsdl.
> Sometimes quitting and reopening the image does the trick as well,
> sometimes it doesn't - I don't see a pattern there.
>
> Is there a easy way to reset a whole web service at once?
>
> Thank you,
>
> Peter

Reply | Threaded
Open this post in threaded view
|

RE: WebServices.BindingBuilder caches

Peter Goessaert
In reply to this post by Peter Goessaert
Tamara, Steven,

Thank you for the tips.
I had already tried resetting that XMLObjectBinding registry but I now
see why that wasn't such a good idea...

We are moving to 7.4, but this needs to be finished in 7.2 first.

Greetings,

Peter

 

-----Original Message-----
From: Kogan, Tamara [mailto:[hidden email]]
Sent: dinsdag 30 januari 2007 15:20
To: Peter Goessaert; [hidden email]
Subject: RE: WebServices.BindingBuilder caches

In addition to WsdlBinding reset try
"XMLObjectBinding configure" or remove the XML to object binding
(XMLObjectBinding. XMLBindingRegistry) that is related to the wsdl
schema you are updating.

I would suggest upgrading to 7.4.1. There have been quite changes and
bug fixes between 7.2 and 7.4.

Tamara Kogan
Smalltalk development,
Cincom Systems

> -----Original Message-----
> From: Peter Goessaert [mailto:[hidden email]]
> Sent: Tuesday, January 30, 2007 9:13 AM
> To: [hidden email]
> Subject: WebServices.BindingBuilder caches
>
> Hallo,
>
> In VW 7.2.1 I have a webservice defined in some #wsdlSchema method.
> But when I make changes to that wsdl, and reload it via
>
>  WebServices.WsdlBinding loadWsdlBindingFrom: ...
>
> the soap (un)marshaling still uses the formerly loaded wsdl, as if it
is
> cached somewhere.
>
> Trying to reset WebServices.WsdlBinding and WebServices.WsdlService
does
> not help, nor does initializing the BindingBuilder.
>
> When I start from a blank image without any webservices code, and then

> load my application, everything works as expected following the
updated
> wsdl.
> Sometimes quitting and reopening the image does the trick as well,
> sometimes it doesn't - I don't see a pattern there.
>
> Is there a easy way to reset a whole web service at once?
>
> Thank you,
>
> Peter