SOAP one way message exception

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Peter Goessaert
> Sent: Tuesday, June 08, 2010 10:10 AM
> To: [hidden email]
> Subject: [vwnc] SOAP one way message exception
>
> Hello,
>
>  
>
> Does VW (7.7) support one way messages in SOAP?
>
> I have been playing with it a little bit and I always get a
> "Some xml content was expected" exception.
>
>  
>
> I used the wsdl from this link:
> http://dev.w3.org/cvsweb/2004/ws/addressing/test-cases/Microso

>
> I had the wizard create all classes and the opentalk server.
> (only change I made to the wsdl was the address <soap:address
> location="http://localhost:16000/TestOneWay"/>).
>
>  
>
> There is a one way operation named Ping, execution of this
> Ping throws the exception.
>
>  
>
> Strange thin is that here
>
>  
>
> SOAPRequest >> replyClass
>
>                 ^self isOneWay
>
>                                ifTrue: [OneWayReply]
>
>                                ifFalse: [SOAPReply ]
>
>  
>
> the isOneWay test gives true, but a little further on there
> is an attempt to parse the xml from the HTTP 200 response:
>
>  
>
> XMLObjectMarshalingManager readDocumentFrom: httpEntity
>
>  
>
> and then the exception occurs.
>
> So it seems to get the fact that it's one-way, but still
> tries to parse some xml afterwards.
>
>  
>
> Any ideas on what's going wrong here?
>
>  
>
> Thanks,
>
> Peter
>
>  
>
>  
>
>  
>
>

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Peter Goessaert
> Sent: Tuesday, June 08, 2010 10:10 AM
> To: [hidden email]
> Subject: [vwnc] SOAP one way message exception
>
> Hello,
>
>
>
> Does VW (7.7) support one way messages in SOAP?
>
> I have been playing with it a little bit and I always get a
> "Some xml content was expected" exception.
>
>
>
> I used the wsdl from this link:
> http://dev.w3.org/cvsweb/2004/ws/addressing/test-cases/Microso

>
> I had the wizard create all classes and the opentalk server.
> (only change I made to the wsdl was the address <soap:address
> location="http://localhost:16000/TestOneWay"/>).
>
>
>
> There is a one way operation named Ping, execution of this
> Ping throws the exception.
>
>
>
> Strange thin is that here
>
>
>
> SOAPRequest >> replyClass
>
>                 ^self isOneWay
>
>                                ifTrue: [OneWayReply]
>
>                                ifFalse: [SOAPReply ]
>
>
>
> the isOneWay test gives true, but a little further on there
> is an attempt to parse the xml from the HTTP 200 response:
>
>
>
> XMLObjectMarshalingManager readDocumentFrom: httpEntity
>
>
>
> and then the exception occurs.
>
> So it seems to get the fact that it's one-way, but still
> tries to parse some xml afterwards.
>
>
>
> Any ideas on what's going wrong here?
>
>
>
> Thanks,
>
> Peter
>
>
>
>
>
>
>
>

> -----Original Message-----
> From: Peter Goessaert [mailto:[hidden email]]
> Sent: Tuesday, June 08, 2010 11:28 AM
> To: Kogan, Tamara; [hidden email]
> Subject: RE: [vwnc] SOAP one way message exception
>
> Hi Tamara,
>
> actually that's exactly how I'm testing it:
>
> 1. take a vanilla 7.7 image & load webservice wizard parcel
> (and thus the prerequisites)
> 2. generate stuff from the WSDL (Classes, Opentalk server)
> 3. startup the generated  opentalk server
> 4. send the ping the way you do it
>
> Do I miss something?
>
> Greetings,
> Peter
>
>
>
> ________________________________________
> Van: Kogan, Tamara [[hidden email]]
> Verzonden: dinsdag 8 juni 2010 16:54
> Aan: Peter Goessaert; [hidden email]
> Onderwerp: RE: [vwnc] SOAP one way message exception
>
> I tried the WSDL and #ping operation works. The one-way
> operation sends a message that is defined as:
> <message name="PingMessageIn">
>   <part name="data" element="s0:Ping"/>
> </message>
> <s:complexType name="Ping">
>  <s:simpleContent>
>    <s:extension base="s:string"/>
>       </s:simpleContent>
> </s:complexType>
>
>
> To send the message you need to provide input parameters for
> the operation:
> arg1 := XN.Ping new
>         value: 'string';
>         yourself.
> client ping: arg1.
>
> There is no reply. The result of #ping invocation is nill.
>
> HTH,
> Tamara Kogan
> Smalltalk development,
> Cincom Systems
>
>
> > -----Original Message-----
> > From: [hidden email]
> > [mailto:[hidden email]] On Behalf Of Peter Goessaert
> > Sent: Tuesday, June 08, 2010 10:10 AM
> > To: [hidden email]
> > Subject: [vwnc] SOAP one way message exception
> >
> > Hello,
> >
> >
> >
> > Does VW (7.7) support one way messages in SOAP?
> >
> > I have been playing with it a little bit and I always get a
> > "Some xml content was expected" exception.
> >
> >
> >
> > I used the wsdl from this link:
> > http://dev.w3.org/cvsweb/2004/ws/addressing/test-cases/Microso
> ft/2005Mar-0209/service.wsdl?rev=1.1
> >
> > I had the wizard create all classes and the opentalk server.
> > (only change I made to the wsdl was the address <soap:address
> > location="http://localhost:16000/TestOneWay"/>).
> >
> >
> >
> > There is a one way operation named Ping, execution of this
> > Ping throws the exception.
> >
> >
> >
> > Strange thin is that here
> >
> >
> >
> > SOAPRequest >> replyClass
> >
> >                 ^self isOneWay
> >
> >                                ifTrue: [OneWayReply]
> >
> >                                ifFalse: [SOAPReply ]
> >
> >
> >
> > the isOneWay test gives true, but a little further on there
> > is an attempt to parse the xml from the HTTP 200 response:
> >
> >
> >
> > XMLObjectMarshalingManager readDocumentFrom: httpEntity
> >
> >
> >
> > and then the exception occurs.
> >
> > So it seems to get the fact that it's one-way, but still
> > tries to parse some xml afterwards.
> >
> >
> >
> > Any ideas on what's going wrong here?
> >
> >
> >
> > Thanks,
> >
> > Peter
> >
> >
> >
> >
> >
> >
> >
> >
>

> -----Original Message-----
> From: Peter Goessaert [mailto:[hidden email]]
> Sent: Tuesday, June 08, 2010 12:48 PM
> To: Kogan, Tamara; [hidden email]
> Subject: RE: [vwnc] SOAP one way message exception
>
> Hi Tamara,
>
> Thanks, that works indeed.
> The difference is -and I should have mentioned it of course-
> that I generated a client under WsdlClient.
>
> client := ServicePortWsdlClient fileName: 'service.wsdl'.
> arg1 := Ping new value: ('pol'); yourself.
> client ping: arg1.
>
> Still crashes, also with your server.
> But I can move on now, thanks for that.
>
> Peter
> ________________________________________
> Van: Kogan, Tamara [[hidden email]]
> Verzonden: dinsdag 8 juni 2010 17:49
> Aan: Peter Goessaert; [hidden email]
> Onderwerp: RE: [vwnc] SOAP one way message exception
>
> It looks like you did everything right.
>
> I attached the package with the classes that I created from
> this schema and workspace. I tested the workspace in 7.7. Try
> the package and see if it works for you.
>
>
> Tamara Kogan
> Smalltalk development,
> Cincom Systems
>
>
> > -----Original Message-----
> > From: Peter Goessaert [mailto:[hidden email]]
> > Sent: Tuesday, June 08, 2010 11:28 AM
> > To: Kogan, Tamara; [hidden email]
> > Subject: RE: [vwnc] SOAP one way message exception
> >
> > Hi Tamara,
> >
> > actually that's exactly how I'm testing it:
> >
> > 1. take a vanilla 7.7 image & load webservice wizard parcel
> > (and thus the prerequisites)
> > 2. generate stuff from the WSDL (Classes, Opentalk server)
> > 3. startup the generated  opentalk server
> > 4. send the ping the way you do it
> >
> > Do I miss something?
> >
> > Greetings,
> > Peter
> >
> >
> >
> > ________________________________________
> > Van: Kogan, Tamara [[hidden email]]
> > Verzonden: dinsdag 8 juni 2010 16:54
> > Aan: Peter Goessaert; [hidden email]
> > Onderwerp: RE: [vwnc] SOAP one way message exception
> >
> > I tried the WSDL and #ping operation works. The one-way
> > operation sends a message that is defined as:
> > <message name="PingMessageIn">
> >   <part name="data" element="s0:Ping"/>
> > </message>
> > <s:complexType name="Ping">
> >  <s:simpleContent>
> >    <s:extension base="s:string"/>
> >       </s:simpleContent>
> > </s:complexType>
> >
> >
> > To send the message you need to provide input parameters for
> > the operation:
> > arg1 := XN.Ping new
> >         value: 'string';
> >         yourself.
> > client ping: arg1.
> >
> > There is no reply. The result of #ping invocation is nill.
> >
> > HTH,
> > Tamara Kogan
> > Smalltalk development,
> > Cincom Systems
> >
> >
> > > -----Original Message-----
> > > From: [hidden email]
> > > [mailto:[hidden email]] On Behalf Of Peter Goessaert
> > > Sent: Tuesday, June 08, 2010 10:10 AM
> > > To: [hidden email]
> > > Subject: [vwnc] SOAP one way message exception
> > >
> > > Hello,
> > >
> > >
> > >
> > > Does VW (7.7) support one way messages in SOAP?
> > >
> > > I have been playing with it a little bit and I always get a
> > > "Some xml content was expected" exception.
> > >
> > >
> > >
> > > I used the wsdl from this link:
> > > http://dev.w3.org/cvsweb/2004/ws/addressing/test-cases/Microso
> > ft/2005Mar-0209/service.wsdl?rev=1.1
> > >
> > > I had the wizard create all classes and the opentalk server.
> > > (only change I made to the wsdl was the address <soap:address
> > > location="http://localhost:16000/TestOneWay"/>).
> > >
> > >
> > >
> > > There is a one way operation named Ping, execution of this
> > > Ping throws the exception.
> > >
> > >
> > >
> > > Strange thin is that here
> > >
> > >
> > >
> > > SOAPRequest >> replyClass
> > >
> > >                 ^self isOneWay
> > >
> > >                                ifTrue: [OneWayReply]
> > >
> > >                                ifFalse: [SOAPReply ]
> > >
> > >
> > >
> > > the isOneWay test gives true, but a little further on there
> > > is an attempt to parse the xml from the HTTP 200 response:
> > >
> > >
> > >
> > > XMLObjectMarshalingManager readDocumentFrom: httpEntity
> > >
> > >
> > >
> > > and then the exception occurs.
> > >
> > > So it seems to get the fact that it's one-way, but still
> > > tries to parse some xml afterwards.
> > >
> > >
> > >
> > > Any ideas on what's going wrong here?
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Peter
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>