Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96036
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.46 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
In-Reply-To: <CA+1HRMmi27_=Be-zo3pYpg3gHG24diADdOvKZ_jB+G0vwztgKQ@mail.gmail.com>
Date: Tue, 20 Sep 2016 15:38:35 +0200
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <3EBE3FDE-46B4-4439-BB0F-3BE2EE88051B@heroku.com>
References: <CA+1HRMmi27_=Be-zo3pYpg3gHG24diADdOvKZ_jB+G0vwztgKQ@mail.gmail.com>
To: Filip Rydlo <filip.rydlo@gmail.com>
Subject: Re: [PHP-DEV] Do You think PHP's SOAP client should have an option to virtuallyAdd (for XSD imports!) missing end-slash in the URI to WSDL? I do!
From: dz@heroku.com (David Zuelke)

I think it should not. Your pull request fixes a problem in that WSDL.

The WSDL is located at the URL =
`https://pg.eet.cz/eet/services/EETServiceSOAP/v3?wsdl`.

It references an XML Schema file at `EETXMLSchema.xsd`, which is a =
relative location, so it's looked for relative to the containing =
document, at =
`https://pg.eet.cz/eet/services/EETServiceSOAP/EETXMLSchema.xsd`.

The correct location is =
`https://pg.eet.cz/eet/services/EETServiceSOAP/v3/EETXMLSchema.xsd`, but =
that's not PHP's problem. You should contact the owner of the service =
and ask them to fix the issue. Not only PHP, but all other clients that =
adhere to the spec will be unable to load this file, so it's in their =
interest to get it resolved.

Failing that, you can

1. use an XML catalog entry on your local system to re-define where =
`EETXMLSchema.xsd` is located;
2. load the WSDL file from the origin URL, cache it locally, and rewrite =
the `schemaLocation` to contain a full relative path =
(`/eet/services/EETServiceSOAP/v3/EETXMLSchema.xsd`) or even an absolute =
URL. Then load that local WSDL.

You really want to do option 2 in production anyway, because otherwise, =
your SoapClient instantiation will fetch the remote WSDL file on each =
instantiation, which slows down your app, and may break things even if =
you don't make a SOAP call if the endpoint is down.

If you want to discuss this further, then the PR on GitHub is the right =
spot for discussing this.


> On 20.09.2016, at 10:02, Filip Rydlo <filip.rydlo@gmail.com> wrote:
>=20
> Hello to all PHP developers!
>=20
>      If You are interested how we could improve SOAPClient a bit,
> please, see my last comment here to understand my *WHYs*. :-)
>=20
>=20
> *https://github.com/php/php-src/pull/2121
> <https://github.com/php/php-src/pull/2121>*
>=20
>=20
>      This pull request is in no way complete. It is just a small start =
to
> let us *track down* the exact code-path *where the problem occurs.*
>=20
>      Sadly, the example scenario (HOW to reproduce) contains a =
*webservice*
> which *only works* from *PCs / I.P.s*  *located  in Czech Republic,
> EU.    *Hopefully,
> some of You also live there... or possibly You have some testing =
virtual
> webserver located there. :)
>=20
>=20
>      *I would be happy to test the new feature!*   But I am still =
unable
> to compile PHP5 from the sources on Debian 8.5 x64  because of some =
module
> called *opcache :-(*
>=20
>=20
>=20
>=20
>       Here is the error I am getting. I am sure it is a well known =
error
> for You ... and You certainly know the solution. Unfortunatelly,  I am =
not
> so good in linux development,  yet.
> Maybe You could tell me how to overcome / workaround this problem,
> please?.That would be GREAT !  :-)
> I already tried all the classical solutions I could *google-out=C2=A8 =
*and
> installing all the dependencies.... did not solve *this*.
>=20
> Thank You so much.
>=20
> Filip The Overtonesinger
>=20
>=20
> ------------------------ ERROR compiling php *5.6.24* sources:
> ----------------------------------------------
>=20
> /bin/bash /home/bob/A_php5/php-src/libtool --silent =
--preserve-dup-deps
> --mode=3Dlink cc -DPHP_ATOM_INC -I/home/bob/A_php5/php-src/include
> -I/home/bob/A_php5/php-src/main -I/home/bob/A_php5/php-src
> -I/home/bob/A_php5/php-src/ext/date/lib -I/usr/include/libxml2
> -I/home/bob/A_php5/php-src/ext/sqlite3/libsqlite
> -I/home/bob/A_php5/php-src/TSRM -I/home/bob/A_php5/php-src/Zend
> -I/usr/include -g -O2 -fvisibility=3Dhidden -DZEND_SIGNALS    -o =
ext/opcache/
> opcache.la -export-dynamic -avoid-version -prefer-pic -module -rpath
> /home/bob/A_php5/php-src/modules  ext/opcache/ZendAccelerator.lo
> ext/opcache/zend_accelerator_blacklist.lo
> ext/opcache/zend_accelerator_debug.lo =
ext/opcache/zend_accelerator_hash.lo
> ext/opcache/zend_accelerator_module.lo ext/opcache/zend_persist.lo
> ext/opcache/zend_persist_calc.lo ext/opcache/zend_file_cache.lo
> ext/opcache/zend_shared_alloc.lo =
ext/opcache/zend_accelerator_util_funcs.lo
> ext/opcache/shared_alloc_shm.lo ext/opcache/shared_alloc_mmap.lo
> ext/opcache/shared_alloc_posix.lo =
ext/opcache/Optimizer/zend_optimizer.lo
> ext/opcache/Optimizer/pass1_5.lo ext/opcache/Optimizer/pass2.lo
> ext/opcache/Optimizer/pass3.lo =
ext/opcache/Optimizer/optimize_func_calls.lo
> ext/opcache/Optimizer/block_pass.lo
> ext/opcache/Optimizer/optimize_temp_vars_5.lo
> ext/opcache/Optimizer/nop_removal.lo
> ext/opcache/Optimizer/compact_literals.lo =
ext/opcache/Optimizer/zend_cfg.lo
> ext/opcache/Optimizer/zend_dfg.lo ext/opcache/Optimizer/dfa_pass.lo
> ext/opcache/Optimizer/zend_ssa.lo =
ext/opcache/Optimizer/zend_inference.lo
> ext/opcache/Optimizer/zend_func_info.lo
> ext/opcache/Optimizer/zend_call_graph.lo =
ext/opcache/Optimizer/zend_dump.lo
> Reloading web server: apache2 failed!
> Apache2 is not running ... (warning).
> Makefile:870: recipe for target 'ext/opcache/opcache.la' failed
> make: *** [ext/opcache/opcache.la] Error 1