Dynamic WSDL - Published Endpoint is relative to Schema Loc

[jbradfor]

All of our Endpoints must go through an ESB.  We also would like to be able
to use the Dynamic WSDL (?WSDL).  Therefore, we set it up like this, where
the published endpoint is the ESB path.

        <!-- Simple JAXWS Frontend  -->
    <jaxws:endpoint 
        id="LocationInformationServiceJAXWS" 
        xmlns:lis="http://service.xxxxx.com/locationinformationservice/v1";      
                        
        address="/LocationInformationService"
        wsdlLocation="/wsdl/LocationInformationService.wsdl"  
        publishedEndpointUrl="${lis.soap.publishedEndpointUrl}"
        serviceName="lis:LocationInformationService">
        <jaxws:implementor><ref bean="lis"/></jaxws:implementor>
        <jaxws:schemaLocations>
        
<jaxws:schemaLocation>/wsdl/schema/Automation_Ping.xsd</jaxws:schemaLocation>   
        
        
<jaxws:schemaLocation>/wsdl/schema/Message_LocationInformationService.xsd</jaxws:schemaLocation>
 
        </jaxws:schemaLocations>
        <jaxws:inInterceptors><ref
local="logInbound"/></jaxws:inInterceptors>
        <jaxws:outInterceptors> <ref
local="logOutbound"/></jaxws:outInterceptors>           
    </jaxws:endpoint>

The problem is that the WSDL displayed uses the ESB path as the relative
path for the imported schema.  Like this:

  <import
namespace="http://service.xxxxx.com/locationinformationservice/messages";
schemaLocation="http://esb/router/LocationInformationService/v01?xsd=schema/Message_LocationInformationService.xsd";
/> 

So therefore, when you go to generate from the Dynamic WSDL (i.e. SoapUI) it
fails, because it cannot find the schema.

Anyone know how to resolve this?







-- 
View this message in context: 
http://cxf.547215.n5.nabble.com/Dynamic-WSDL-Published-Endpoint-is-relative-to-Schema-Loc-tp3405282p3405282.html
Sent from the cxf-user mailing list archive at Nabble.com.