You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by jbradfor <jb...@amfam.com> on 2011/03/01 17:46:25 UTC
Dynamic WSDL - Published Endpoint is relative to Schema Loc
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.
Re: Dynamic WSDL - Published Endpoint is relative to Schema Loc
Posted by Freeman Fang <fr...@gmail.com>.
On 2011-3-2, at 上午12:46, jbradfor wrote:
> 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.
Hi,
You mean the link http://esb/router/LocationInformationService/v01?xsd=schema/Message_LocationInformationService.xsd
is invalid?
You can't get a xsd file from that link even from browser?
Btw, what kind of ESB you're using?
Freeman
>
> 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.
--
Freeman Fang
------------------------
FuseSource: http://fusesource.com
blog: http://freemanfang.blogspot.com
twitter: http://twitter.com/freemanfang
Apache Servicemix:http://servicemix.apache.org
Apache Cxf: http://cxf.apache.org
Apache Karaf: http://karaf.apache.org
Apache Felix: http://felix.apache.org