• 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: WOWebServiceRegistrar.setSecurityDelegate failure
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOWebServiceRegistrar.setSecurityDelegate failure


  • Subject: Re: WOWebServiceRegistrar.setSecurityDelegate failure
  • From: Anjo Krank <email@hidden>
  • Date: Tue, 22 Apr 2008 22:24:59 +0200

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
  • Follow-Ups:
    • Re: WOWebServiceRegistrar.setSecurityDelegate failure
      • From: "Mr. Pierre Frisch" <email@hidden>
References: 
 >WOWebServiceRegistrar.setSecurityDelegate failure (From: Jon Nolan <email@hidden>)
 >Re: WOWebServiceRegistrar.setSecurityDelegate failure (From: Mike Schrag <email@hidden>)
 >Re: WOWebServiceRegistrar.setSecurityDelegate failure (From: "Mr. Pierre Frisch" <email@hidden>)
 >Re: WOWebServiceRegistrar.setSecurityDelegate failure (From: Jon Nolan <email@hidden>)
 >Re: WOWebServiceRegistrar.setSecurityDelegate failure (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: WOWebServiceRegistrar.setSecurityDelegate failure
  • Next by Date: WOEventDisplay (WOEvent logging password)
  • Previous by thread: Re: WOWebServiceRegistrar.setSecurityDelegate failure
  • Next by thread: Re: WOWebServiceRegistrar.setSecurityDelegate failure
  • Index(es):
    • Date
    • Thread