axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1472) WSDLUtils.getAddressFromPort does not follow imports
Date Thu, 22 Jul 2004 21:28:18 GMT
The following comment has been added to this issue:

     Author: Aaron Hamid
    Created: Thu, 22 Jul 2004 2:26 PM
A little more research: Parser uses lookupImports to find and include imports.  This code
inspects the 'schemaLocation' attribute, not 'location' attribute.  If I change my import
element to use 'schemaLocation' attribute, then the parser will actually correctly fetch the
imported document (I can tell by web server access log).

lookupImports then calls populate() method with several parameters.

populate() first does some schema/type population stuff, then does, in sequence:


It appears perhaps that arbitrary elements cannot be imported?
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1472
    Summary: WSDLUtils.getAddressFromPort does not follow imports
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
             WSDL processing
             1.2 Alpha
             1.2 Beta

   Reporter: Aaron Hamid

    Created: Thu, 22 Jul 2004 2:02 PM
    Updated: Thu, 22 Jul 2004 2:26 PM
Environment: tested against axis 1.1 and axis 1.2 (latest release zip)

I have a port in a standard WSDL defined like:

<wsdl:port binding="impl:SomeServiceSoapBinding" name="SomeService">
  <wsdl:import namespace="urn:SomeService" location="http://somehost/host.wsdl" />

host.wsdl on somehost contains:

<?xml version="1.0" encoding="UTF-8"?>
<wsdlsoap:address location="http://someotherhost:90/axis/services/SomeService"/>

I call setImports(true) on the org.apache.axis.wsdl.gen.Parser object, and call run(), where
doc is the pre-parsed org.w3c.dom.Document of the WSDL file:

parser = new Parser();
parser.setImports(true);, doc);

I hand this parser to the constructor of Service:

Service service = new Service(parser, aqname);

Now I recieve this error when invoking the service:

"No client transport named 'null' found!"

It appears that the Axis Service class obtains the wsdl Port object, then calls WSDLUtils.getAddressFromPort(port).
 This method returns null.

I would expect the setImports(true) flag to indicate to the Parser to import any referenced
documents and for the getAddressFromPort() method to find the correct address.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message