From: Matthew Peters <matthew.f.pet...@googlemail.com>
Date: Thu, 20 Nov 2008 10:36:27 -0800 (PST)
Local: Thurs 20 Nov 2008 18:36
Subject: Re: Consuming SSL secured web services
The way I _think_ this works (though it is 2 years since I last looked
at this bit of the code) is as follows: 1. the Soap_Proxy calls setWSDLTypes 2. setWSDLTypes calls the SDO_DAS_XML::create (as shown in the message below) 3. the SDO_DAS_XML code calls the Tuscany SDO code passing the URL 4. The Tuscany SDO code calls fopen() or something similar 5. This is picked up by the PHP file wrapper (see e.g. http://uk3.php.net/fopen) 6. PHP looks at the scheme (hhtps) and handles the open So, I _think_ this comes down to the same behaviour that you would get
So, does
Matthew
On 19 Nov, 17:43, silvanojr <silvan...@gmail.com> wrote:
> Adding the error message.
> [19-Nov-2008 12:42:27] PHP Fatal error: Uncaught
> thrown in /usr/share/pear/SCA/Bindings/soap/Proxy.php on line 104
> Silvano
> On 19 nov, 12:12, "Silvano Girardi Jr" <silvan...@gmail.com> wrote:
> > Lady and Gentlemen :)
> > I am trying to consume a SSL secured web service and I need to use a
> > I was doing changes in the SCA_Bindings_soap_Proxy to accept the
> > Please let me know if I am wrong in my assumption, otherwise, does
> > Appreciate you help. This is a high priority for me.
> > Thanks,
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||