Bug 749375 - [RFE] Dynamic WSDL retrieval over HTTP using ?wsdl convention doesn't work for Aviary
Summary: [RFE] Dynamic WSDL retrieval over HTTP using ?wsdl convention doesn't work fo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-aviary
Version: Development
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-26 20:31 UTC by Pete MacKinnon
Modified: 2016-05-26 20:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 20:01:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Pete MacKinnon 2011-10-26 20:31:59 UTC
Technical Debt:

Clients should be able to retrieve the Aviary WSDL and imported schema definitions dynamically by using the advertised URL appended with ?wsdl like:

http://localhost:9091/services/query?wsdl

However, this doesn't currently work and results in a parse error from the Axis2/C engine.

XML Parsing Error: no element found
Location: http://localhost:9091/services/query?wsdl
Line Number 1, Column 1:

It's unclear if this is a matter of REST configuration or perhaps the <soap:address location=...> element plays a role in WSDL retrieval.

Comment 1 Pete MacKinnon 2011-10-27 14:24:45 UTC
After further investigation and code walkthrough, not looking great. Axis2/C doesn't support dynamic WSDL generation but it does allow for service configuration to attach the WSDL file.

<parameter name="wsdl_path" locked="xsd:false">/var/lib/services/query/aviary-query.wsdl</parameter>

However, that just renders the WSDL file literally and doesn't parse the <xsd:import ...> statement so no way to render the types files unless they were hosted somehow from the stack or elsewhere over HTTP.


Note You need to log in before you can comment on or make changes to this bug.