• 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
WOWebServiceClient vs. WSDL proxy classes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WOWebServiceClient vs. WSDL proxy classes


  • Subject: WOWebServiceClient vs. WSDL proxy classes
  • From: Michael Engelhart <email@hidden>
  • Date: Sun, 23 May 2004 08:56:12 -0500

I'm looking into using WO to consume web services from a vendor. Looking at the documentation on how WO acts as a client, it seems that the way this is done is by creating a WOWebServiceClient class and then creating methods that call the invoke() method on that object. The way I've dealt with WebServices in a non-WO app is to use the generated proxy classes that wsdl2java creates (and I noticed that there is a modification to this available that will generate output where each proxy class has key-value coding in it as well which is nice) and essentially just write directly to the objects. My concern with this is that in the system I'm accessing, one of the services generates over a 100 classes and writing that code is going to be maze of object accessors.

So I guess my question is, is the WO way any better? Because the documentation is totally simplistic (the sample is to access a calculator webservice) and the Amazon client sample is very broken (I believe the webservice model at Amazon has changed since that sample was created), I'd post the WSDL files here of the services I need to talk to but I can't because of an NDA. Also the webservice has security tokens and other message headers that need to be passed in each request that I also can't figure out how pass in using the WOWebServiceClient.

The bottom line is that since I'm going to build the app in WebObjects, I'd rather invoke the webservices using the WO way but without more documentation it's going to be pretty difficult to do. Does anyone have any experience in building real-world WebService consumers using WO that can steer me in the right direction? BTW, I've gone to Xmethods and built about 5 small applications using WO (temperature lookups, postal code lookups, etc). but all of the samples I could find there are again very simple and nothing like what I'm going to need to help me understand how WO handles things for complex services. The Amazon sample is better but because it's broken and I don't want to have to debug sample code if I can avoid it I thought I'd check here.


Mike Engelhart http://www.eztrip.com/ _______________________________________________ webobjects-dev mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev Do not post admin requests to the list. They will be ignored.


References: 
 >WO & Background Services (From: Lotsa Cabo <email@hidden>)

  • Prev by Date: Re: detail WODisplayGroup & FetchSpec
  • Next by Date: ".lasso" extension
  • Previous by thread: Re: WO & Background Services
  • Next by thread: installing 5.2 for the second time
  • Index(es):
    • Date
    • Thread