• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: SOAP and WebServices
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SOAP and WebServices


  • Subject: Re: SOAP and WebServices
  • From: Alexander von Below <email@hidden>
  • Date: Tue, 16 Aug 2005 22:03:17 +0200

No, it's the first case unfortunately: We want to set new parameters for every invocation, and get new data. However, we thought that alloc'ing and release'ing the objects each time would be wasteful.

It is a work-around solutions though to alloc and release the objects each time.

Thanks

Alex


Am 16.08.2005 um 21:55 schrieb Byron Wright:

You could just instantiate a new SOAPRequest invocation object for each
request? Are you wanting to request new data or just reuse the SOAPRequests
results?


If it's the second case then you could just copy (or retain) the results
dictionary returned from getResultsDictionary?


-----Original Message-----
From: cocoa-dev-bounces+byron=email@hidden
[mailto:cocoa-dev-bounces+byron=email@hidden] On
Behalf Of Alexander von Below
Sent: Tuesday, August 16, 2005 12:06 PM
To: email@hidden
Subject: SOAP and WebServices

Dear List,

I am not sure if this is the right place, but I can not find any
better list.

We are building a Cocoa App which heavily relies on SOAP requests,
and we are using the WebServicesCore.framework (1)

Generally that works OK, but when we are trying to re-use one of our
request (a subclass of WSGeneratedObj), the app crashes.

With re-use, I mean something like this (this is an example only):

returnedResult =  [SOAPRequest getResultDictionary];

// this call works

[SOAPRequest reset];
returnedResult =  [SOAPRequest getResultDictionary];
// this call fails

In the second call, a "EXC_BAD_ACCESS" is triggered in
HTTPClosureSource::processBuffer, after our app called

WSMethodInvocationScheduleWithRunLoop(invocation, CFRunLoopGetCurrent
(), wsGeneratedMode); and the run loop is running.

(This seems to be a genuine bug, and I will file it as such)

However my questions are:

- Has someone found a workaround to "re-use" the objects?
- Is it worth to abandon the WebServices framework altogether, and
look for alternatives?

For those who are looking to use SOAP in their Cocoa apps, I have a
nice little sample using the google SOAP api. I will "polish" it a
bit more and post it, but if somebody wants it right now then please
send me a message.

Thanks and bye

Alex




1) http://developer.apple.com/documentation/Networking/Conceptual/ UsingWebservices/

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40bluebearstudio.com


This email sent to email@hidden


--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.9/72 - Release Date: 8/14/2005



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.9/72 - Release Date: 8/14/2005





_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: SOAP and WebServices
      • From: Scott Ellsworth <email@hidden>
  • Prev by Date: RE: SOAP and WebServices
  • Next by Date: Re: core data during startup (solved)
  • Previous by thread: RE: SOAP and WebServices
  • Next by thread: Re: SOAP and WebServices
  • Index(es):
    • Date
    • Thread