Re: WOWebServiceRegistrar.setSecurityDelegate failure
Re: WOWebServiceRegistrar.setSecurityDelegate failure
- Subject: Re: WOWebServiceRegistrar.setSecurityDelegate failure
- From: Jon Nolan <email@hidden>
- Date: Tue, 22 Apr 2008 16:52:13 -0600
- Organization: Web Dynamics - A Division of iCentris
Thank you gentlemen. Your help is appreciated. I'll report back once I'm able to work on your suggestions.
Jon
Mr. Pierre Frisch wrote:
Without going into too much details when WebServices for WebObjects were
created with Axis 1.0 type information in WDSL document was optional,
WebOjects did not include it. With Axis 1.1 and event more for Axis 1.4
it became required for custom types. This was fixed in WO 5.4.x
unfortunately it took us multiple iterations to cover all the cases (and
there are many). WebObjects 5.3.x and Axis 1.1 work if you do not use
any custom types i.e. you do not have your own serializer/deserializer.
As Anjo said there are some major difference in the registration between
5.4.0/5.4.1 and 5.4.2. You should use the later. I have written a quick
test case and at least it does not throw the exception you are seeing.
As I said WO 5.4.2 is available with the iPhone SDK.
Cheers
Pierre
--
Pierre Frisch
email@hidden
On Apr 22, 2008, at 13:24, Anjo Krank wrote:
5.4.1 wouldn't even start without serious prodding, there where pretty
serious bugs in registering a service. In 5.4.2, all the issues I have
left are in axis itself and not really under Pierre's control to fix
(which are related to special client and server libs). In particular
the bug reported lately (axis 1.4 creates refs for primitive types).
Cheers, Anjo
Am 22.04.2008 um 22:15 schrieb Mike Schrag:
Pierre, if 5.4.x versions all use Axis 1.4 how does moving to 5.4.2
help? Regarding the call to org.apache.xml.security.Init, I'm
sorry, it's extraneous to this conversation and I didn't mean to
post it. I use it for some webservice encryption needs.
Any advice on a somewhat guaranteed stable/working
WebObjects/WOLips/Java/Axis environment for non-trivial webservices
is very, very appreciated.
I have been using 5.3 with web services for several years without
problems, though this very much depends on what is on the other side
of the service. I know Anjo had several issues with 5.4.0/5.4.1 and
web services, though Pierre has fixed all of these in 5.4.2 as far as
I know. I have an app that I can run now with 5.4.2 or 5.3 without
any issues, though I don't know about your particular case. I
recommended trying 5.3 first because it has been out for quite a
while and most of the issues are known, or at the very least, as
Pierre recommends, download 5.4.2 from the iPhone SDK and try that.
I wouldn't spend any time trying to diagnose this in any environment
other than 5.3 or 5.4.2 because I think it's probably a waste of time
since work was specifically done on this area.
ms
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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