Re: WO Web Services + Cocoa
Re: WO Web Services + Cocoa
- Subject: Re: WO Web Services + Cocoa
- From: Anjo Krank <email@hidden>
- Date: Fri, 19 May 2006 16:04:07 +0200
These normally appear in the tag declaration as <sometag
xmlns:ns1="http://blabla";>. It might be that they go away if you
start your namespace with sth more sensible than "http://";...
Am 19.05.2006 um 15:49 schrieb Mike Schrag:
Yes, I agree .. The ns1: sounds fishy, and I don't know WHY it is
being produced. I only know that it is by printing the result
dictionary, and that is the value of the key.
For what it's worth, I have not SEEN an ns2. However, there are
tns1: and tns2: references inside of the WSDL. I wonder if you had
classes in multiple packages that are returned, if that might
result in an ns2 coming back for the second package? I think that
ns1 and ns2 are namespace aliases?
The reference to wsmakestubs and invalid indentifiers is
specifically referring to this problem. If you use WSMakeStubs
stock (at least with WO 5.3 as you mentioned -- I had not tried
this on older versions), the key that it uses for the return value
(sans ns1:) just doesn't exist in the dictionary and will return nil.
ms
On May 19, 2006, at 9:25 AM, Marc Respass wrote:
Mike,
I've been dealing with this for over a year. Thanks for the
valuable info.
I have a question about the return value. The "ns1:" in the key is
new since WO 5.3 (more likely, the version of Axis that ships with
it). I guessed "ns1" to stand for namespace 1 so I figured there
is the possibility of "ns2" showing up and felt uncomfortable
modifying my key to start with "ns1:". I wrote a new method to
look for the first ":" and strip everything up to and including
the colon.
What do you think of that? If you have an Axis client, of course,
everything works fine. You said that WSMakeStubs "doesn't produce
a valid identifier for retrieving a WO web service return value."
What does that mean? I haven't done enough research to understand
why Axis is now generating that "ns1:".
Thanks a lot
Marc
On May 19, 2006, at 8:16 AM, Mike Schrag wrote:
I just went through the pain of getting a cocoa client to call a
WO Web Service. For anyone who would like to avoid this same
pain, I wrote up the steps in the Wikibook:
http://en.wikibooks.org/wiki/Programming:WebObjects/Web_Services/
Web_Service_Provider#Consuming_with_WebServicesCore.framework
It's actually a relatively small set of changes required to get
things working properly, and it works quite well once the changes
are made.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40logicunited.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden