ZF-8052: SoapClient is unable to handle <xsd:import>

Issue Type:
New Feature
Created:
2009-10-12T02:40:56.000+0000
Last Updated:
2010-10-28T00:19:04.000+0000
Status:
Resolved
Fix version(s):
    Reporter:
    Jan Pieper (jpieper)
    Assignee:
    Jan Pieper (jpieper)
    Tags:
    • Zend_Soap_Client
    Related issues:
    Attachments:

    Description

    Create a new Zend_Soap_Client_* that can handle .

    www.example.com/service?xsd=1">
        
    ...

    SoapClient seems to be unable to handle and is causing an endless loop.

    Workaround: * download WSDL and XSD files * change schemaLocation-URLs to local files * initialize SoapClient with modified WSDL file

    Works fine, but I don't know whether this is the best way to solve this problem.

    Comments

    Posted by Benjamin Eberlei (beberlei) on 2009-10-23T13:03:11.000+0000

    Do you already have code for this? then please contribute it :-)

    Does this bug appear on PHPs SoapClient also? If yes, please report a bug on php.net

    Posted by Jan Pieper (jpieper) on 2010-10-28T00:18:56.000+0000

    It has nothing todo with these elements. The problem is, that the JAX-WS server seems to be unable to handle HTTP/1.0 requests and sends HTTP/1.1 responses. Changing HTTP version to 1.1 didn't help (SoapFault: www.php.net/stream_context_create" rel="nofollow">WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from "..."). It's required to set "Connection: close" header using a stream context ([stream_context_create()).

    $context = stream_context_create(array(
    'http' => array('header' => 'Connection: close')
));

$client = new Zend_Soap_Client('', array(
    'soap_version'   => SOAP_1_1,
    'stream_context' => $context
));