I will definitely have a look at this one. Expect an RC2 :) Arnaud. > The crux of this particular problem with Net/DIME.php seems to lie > in SOAP/Transport.php line 56: > > res = @include_once($transport_include); > > and SOAP/Transport/HTTP.php line 33: > > require_once 'Net/DIME.php'; > > It seems SOAP/Transport/HTTP.php tries to require Net/DIME.php, and > because of the @ an inclusion error is not reported, but the script is > stopped because the require_once 'Net/DIME.php' in > SOAP/Transport/HTTP.php > throws a fatal error, which even @ can't avoid. > > This inclusion/require should not be happening in this class > anyway as it > is already included (or atleast tried to) in SOAP/Base.php, > with adequate > error handling if it's still needed in SOAP_Base. > > The same fatal error problem could still exist if > SOAP/Base.php gives a > fatal error when it is required in SOAP/Transport/HTTP.php , but let's > assume it is always already included if we call it from > SOAP_Transport. > > Also SOAP_Transport_HTTP is extending the wrong class, > SOAP_Base_Object, > instead of SOAP_Base, from which it uses the _makeDIMEMessage and > _decodeMimeMessage methods in its _parseResponse method. > > This should also resolve Brodie Thiesfield's problem in post: > "[SOAP] bug in _decodeDIMEMessage" (7/16/2003) > And perhaps also Will Green's Mime echo problem in post: > "PEAR::SOAP server handling MIME attachemnts" (7/30/2003) > > If we correct the parent class it should now give a > SOAP_Fault error in > $this->fault in the case Net/DIME.php or Net/Mime.php doesn't > exist when > calling _makeDIMEMessage or _decodeMimeMessage. That is if the method > _parseResponse would return false if the _makeDIMEMessage or > _decodeMimeMessage returned a PEAR_Error. > > The attached patch diff for SOAP/Transport/HTTP.php, SOAP-0.8RC1 > should fix all these problems. > > > - Pim Broekhof > > "Javier Muniz" <jmuniz@granicus.com> wrote in message > news:8CAA2F1AC7B96C43974814DD3D95EF982EF46C@sfomail-01.granicu snt.granicus.com... > One thing that I've noticed is that a script using PEAR::SOAP dies with no > error message when it tries to instatiate a class that has not been defined. > This is not just a problem with missing dependencies, but also if you > accidentally instatiate a class before you have loaded it's include file. > > Has anyone else noticed this? > > -Javier > > -----Original Message----- > From: Abdul-Wahid Paterson [mailto:aw@lintrix.net] > Sent: Wednesday, August 27, 2003 4:14 PM > To: Will Green > Cc: soap@lists.php.net > Subject: Re: [SOAP] soap problems revisited > > > > > > > Did you use pear to install SOAP, or did you just unzip the SOAP > > Package? > > > > I ask because pear shouldn't let you install SOAP without Net_DIME. > > No I didn't use pear to install SOAP. I just unzipped the tar.gz file. My > mistake, just strange that it didn't generate any error message. > > -- > Abdul-Wahid Paterson > > Lintrix Networking & Communications ltd. > Web: http://www.lintrix.net/ > Tel: +44 20 8904 2348 > Email/Jabber: aw@lintrix.net > -------------------------------------------------------------------- > Web-Hosting | Development | Security | Consultancy | Domains > -------------------------------------------------------------------- -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
