Just to make sure I understand, you deploy the two endpoints
(the consumer targetting the provider proxying the external web service)
on different nodes in the cluster. And you don't see the wsdl, right ?
This is an unsupported feature. WSDLs descriptions can currently not
be retrieved from remote endpoints. There is a JIRA for that.
The workaround is to specify the wsdl on the consumer endpoint
by embedding it in the SU.
On 3/23/07, timbo <[EMAIL PROTECTED]> wrote:
i'm seeing a similar problem.
have 2 SUs, an http provider endpoint and an http consumer endpoint,
currently acting as a web service "bridge" through smx.
when i deploy them in one SA, all is well, and i can invoke the wsdl and
the
web service operations.
when i deploy them in seperate SAs in the same smx, all is well too.
but when i deploy the separate SAs to different smx instances (default
smx/amq config, different machines, same subnet, no ports blocked), i get
404 asking for wsdl, and 302 on soap request to consumer.
here is my http provider endpoint:
<http:endpoint service="fts:FTSecurityService"
endpoint="FTSecurityServiceSoap" role="provider"
locationURI="
http://localhost:80/FTSecurityService/FTSecurityService.asmx";
wsdlResource="
http://localhost:80/FTSecurityService/FTSecurityService.asmx?wsdl";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true" />
here is my http consumer endpoint:
<http:endpoint service="fts:FTSecurityConsumer"
endpoint="FTSecurityServiceSoap" role="consumer"
targetService="fts:FTSecurityService"
locationURI="
http://0.0.0.0:8192/FTSecurityService/FTSecurityService.asmx";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true" />
gnodet wrote:
>
> The usual cause is that at the time the http SU is started,
> the target endpoint is not activated or does not have any
> wsdl description. SU are started in the order they are listed
> in the SA jbi descriptor. So make sure the right order is used,
> and that your target endpoint has a WSDL description.
>
>
--
View this message in context:
http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9628592
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
