You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by "Maxim Y. Tebenev" <mt...@softech.ru> on 2007/03/16 19:28:51 UTC
Obtaining wsdl for consumer HTTP endpoint
Hi Guys,
When I'm sending request to ESB for WSDL (http://localhost:8192/myep?wsdl),
I get 404 error.
Also I've found following code in ConsumerProcessor.java:
if (query != null && query.trim().equalsIgnoreCase("wsdl")) {
String uri = request.getRequestURI();
if (!uri.endsWith("/")) {
uri += "/";
}
uri += "main.wsdl";
response.sendRedirect(uri);
return;
}
It seems, that ServiceMix redirects (302) user to mail.wsdl page which
doesn't exists in my configuration. So, how to configure well HTTP consumer
endpoint to allow wsdl responding?
Thanks in advance!
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9520105
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by Guillaume Nodet <gn...@gmail.com>.
It seems that the external service has not been discovered somehow.
You should try to raise the log level and see what happens when you start
one node or shut it down. You can also try the clustered examples
in the distribution.
On 3/23/07, timbo <bi...@ieee.org> wrote:
>
>
> yes you understand correctly. the wsdl problem is minor now. more
> troublesome
> is failure invoking the service. below is part of the stack trace.
>
> i have each smx instance with a unique name. is there some special config
> of the cluster required for this to work?
>
>
> DEBUG - jetty - POST
> /FTSecurityService/FTSecurityService.asmx/ HTTP/1.0
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime, multipart/related, text/*
> User-Agent: Axis/1.4
> Host: 10.90.116.165:8192
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction: "FTSecurity/Login"
> Content-Length: 352
>
> WARN - jetty -
> /FTSecurityService/FTSecurityService.asmx/
> javax.jbi.messaging.MessagingException: Could not find route for exchange:
> InOut[
> id: ID:127.0.0.1-1117f480065-3:1
> status: Active
> role: provider
> service: {FTSecurity}FTSecurityService
> operation: {FTSecurity}Login
> in: <?xml version="1.0" encoding="UTF-8"?><Login xmlns="FTSecurity"
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> "><userName>admin</userName><password>jeahjfallm</password></Login>
> ] for service: {FTSecurity}FTSecurityService and interface: null
> at
> org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
> DefaultBroker.java:295)
> ...
>
>
>
>
>
> gnodet wrote:
> >
> > 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 <bi...@ieee.org> 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/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9641744
> 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/
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by timbo <bi...@ieee.org>.
yes you understand correctly. the wsdl problem is minor now. more troublesome
is failure invoking the service. below is part of the stack trace.
i have each smx instance with a unique name. is there some special config
of the cluster required for this to work?
DEBUG - jetty - POST
/FTSecurityService/FTSecurityService.asmx/ HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: 10.90.116.165:8192
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "FTSecurity/Login"
Content-Length: 352
WARN - jetty -
/FTSecurityService/FTSecurityService.asmx/
javax.jbi.messaging.MessagingException: Could not find route for exchange:
InOut[
id: ID:127.0.0.1-1117f480065-3:1
status: Active
role: provider
service: {FTSecurity}FTSecurityService
operation: {FTSecurity}Login
in: <?xml version="1.0" encoding="UTF-8"?><Login xmlns="FTSecurity"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><userName>admin</userName><password>jeahjfallm</password></Login>
] for service: {FTSecurity}FTSecurityService and interface: null
at
org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:295)
...
gnodet wrote:
>
> 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 <bi...@ieee.org> 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/
>
>
--
View this message in context: http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9641744
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <bi...@ieee.org> 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/
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by timbo <bi...@ieee.org>.
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.
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Hi Bruce,
Thanks for the help!
Definitely the problem was in HTTP endpoint configuration. That diagram
helps a lot.
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9574748
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by Bruce Snyder <br...@gmail.com>.
On 3/17/07, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> Hi Guys,
>
> Thank you for advises!
> Unfortunately it doesn't solve my problem. I've debugged SoapEndpoint.java
> and found that ServiceMix cannot determine correct PortType from WSDL
> (reader.readWSDL returns not null, but HttpEndpoint::overrideDefinition
> returns null). I suggest that something wrong with my WSDL. Could you please
> take a look at the WSDL and give an idea what's wrong with that?
>
> Here's my endpoints definition:
>
> <!-- AddressLocationInfo -->
> <http:endpoint service="intraoss:AddressLocationInfoOut"
> endpoint="AddressLocationInfoOut"
> role="provider"
> soap="true"
> soapVersion="1.2"
> locationURI="${intraoss-server-url}/AddressLocationInfo"
>
> wsdlResource="${intraoss-server-url}/AddressLocationInfo?wsdl"/>
>
> <http:endpoint service="intraoss:AddressLocationInfoIn"
> endpoint="AddressLocationInfoIn"
> role="consumer"
> soap="true"
> soapVersion="1.2"
> targetService="intraoss:AddressLocationInfoOut"
>
> locationURI="http://0.0.0.0:8192/AddressLocationInfo/"
> wsdlResource="classpath:AddressLocationInfo.wsdl"
>
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/>
...
> <wsdl:service name="AddressLocationInfo">
> <wsdl:port name="AddressLocationInfoHttpPort"
> binding="tns:AddressLocationInfoHttpBinding">
> <wsdlsoap:address
> location="http://localhost:8192/AddressLocationInfo/"/>
> </wsdl:port>
> </wsdl:service>
Based on the fact that the wsdl:service/wsdl:port@name is
AddressLocationInfoHttpPort, I think that the endpoint might be
incorrectly configured. See this diagram for information on how the
xbean.xml maps to the WSDL:
http://incubator.apache.org/servicemix/5-jbi.html#5.JBI-Concretemodel
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Guys,
One more note on WSDL for HTTP endpoint. I've copied WSDL content from SMX
examples (namely loan-broker-bpel) and got the same result. Could be the
reason outside of WSDL and configuration files?
Best regards, Maxim Tebenev.
--
View this message in context: http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9528845
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by "Maxim Y. Tebenev" <mt...@softech.ru>.
Hi Guys,
Thank you for advises!
Unfortunately it doesn't solve my problem. I've debugged SoapEndpoint.java
and found that ServiceMix cannot determine correct PortType from WSDL
(reader.readWSDL returns not null, but HttpEndpoint::overrideDefinition
returns null). I suggest that something wrong with my WSDL. Could you please
take a look at the WSDL and give an idea what's wrong with that?
Here's my endpoints definition:
<!-- AddressLocationInfo -->
<http:endpoint service="intraoss:AddressLocationInfoOut"
endpoint="AddressLocationInfoOut"
role="provider"
soap="true"
soapVersion="1.2"
locationURI="${intraoss-server-url}/AddressLocationInfo"
wsdlResource="${intraoss-server-url}/AddressLocationInfo?wsdl"/>
<http:endpoint service="intraoss:AddressLocationInfoIn"
endpoint="AddressLocationInfoIn"
role="consumer"
soap="true"
soapVersion="1.2"
targetService="intraoss:AddressLocationInfoOut"
locationURI="http://0.0.0.0:8192/AddressLocationInfo/"
wsdlResource="classpath:AddressLocationInfo.wsdl"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/>
-------------
The following is my WSDL file:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
targetNamespace="http://intraoss.services.com/AddressLocationInfo"
xmlns:tns="http://intraoss.services.com/AddressLocationInfo"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"
xmlns:ns1="http://domain.intraoss.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns3="http://exception.service.intraoss.com"
xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding"
xmlns:ns2="http://exception.services.intraoss.com"
xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://domain.intraoss.com">
<xsd:complexType name="AddressLocationInfoAddress">
<xsd:sequence>
<xsd:element name="address" nillable="true" type="xsd:string"/>
<xsd:element name="city" nillable="true" type="xsd:string"/>
<xsd:element name="state" nillable="true" type="xsd:string"/>
<xsd:element name="zip" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RateCenterAndLata">
<xsd:sequence>
<xsd:element name="lata" nillable="true" type="xsd:string"/>
<xsd:element name="rateCenter" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://intraoss.services.com/AddressLocationInfo">
<xsd:element name="getRateCenterAndLata">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true"
type="ns1:AddressLocationInfoAddress"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="getRateCenterAndLataResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true"
type="ns1:RateCenterAndLata"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://exception.service.intraoss.com">
<xsd:complexType name="FaultInfo">
<xsd:sequence>
<xsd:element name="code" nillable="true" type="xsd:string"/>
<xsd:element name="detailedMessage" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://exception.services.intraoss.com">
<xsd:element name="FaultInfo" type="ns3:FaultInfo"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="getRateCenterAndLataResponse">
<wsdl:part name="parameters"
element="tns:getRateCenterAndLataResponse"/>
</wsdl:message>
<wsdl:message name="FaultInfo">
<wsdl:part name="FaultInfo" element="ns2:FaultInfo"/>
</wsdl:message>
<wsdl:message name="getRateCenterAndLataRequest">
<wsdl:part name="parameters" element="tns:getRateCenterAndLata"/>
</wsdl:message>
<wsdl:portType name="AddressLocationInfoPortType">
<wsdl:operation name="getRateCenterAndLata">
<wsdl:input name="getRateCenterAndLataRequest"
message="tns:getRateCenterAndLataRequest"/>
<wsdl:output name="getRateCenterAndLataResponse"
message="tns:getRateCenterAndLataResponse"/>
<wsdl:fault name="FaultInfo" message="tns:FaultInfo"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AddressLocationInfoHttpBinding"
type="tns:AddressLocationInfoPortType">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="getRateCenterAndLata">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="getRateCenterAndLataRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="getRateCenterAndLataResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="FaultInfo">
<wsdlsoap:fault name="FaultInfo" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AddressLocationInfo">
<wsdl:port name="AddressLocationInfoHttpPort"
binding="tns:AddressLocationInfoHttpBinding">
<wsdlsoap:address
location="http://localhost:8192/AddressLocationInfo/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
--
View this message in context: http://www.nabble.com/Obtaining-wsdl-for-consumer-HTTP-endpoint-tf3416105s12049.html#a9528685
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by Guillaume Nodet <gn...@gmail.com>.
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.
On 3/17/07, Bruce Snyder <br...@gmail.com> wrote:
>
> On 3/16/07, Maxim Y. Tebenev <mt...@softech.ru> wrote:
> >
> > Hi Guys,
> >
> > When I'm sending request to ESB for WSDL (
> http://localhost:8192/myep?wsdl),
> > I get 404 error.
> >
> > Also I've found following code in ConsumerProcessor.java:
> >
> > if (query != null && query.trim().equalsIgnoreCase("wsdl"))
> {
> > String uri = request.getRequestURI();
> > if (!uri.endsWith("/")) {
> > uri += "/";
> > }
> > uri += "main.wsdl";
> > response.sendRedirect(uri);
> > return;
> > }
> >
> > It seems, that ServiceMix redirects (302) user to mail.wsdl page which
> > doesn't exists in my configuration. So, how to configure well HTTP
> consumer
> > endpoint to allow wsdl responding?
>
> The redirect is just fine. Usually a 404 indicates that the SU is
> misconfigured somehow. Can you post the xbean.xml for the
> servicemix-http SU as well as the WSDL for the servicemix-jsr181 SU?
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: Obtaining wsdl for consumer HTTP endpoint
Posted by Bruce Snyder <br...@gmail.com>.
On 3/16/07, Maxim Y. Tebenev <mt...@softech.ru> wrote:
>
> Hi Guys,
>
> When I'm sending request to ESB for WSDL (http://localhost:8192/myep?wsdl),
> I get 404 error.
>
> Also I've found following code in ConsumerProcessor.java:
>
> if (query != null && query.trim().equalsIgnoreCase("wsdl")) {
> String uri = request.getRequestURI();
> if (!uri.endsWith("/")) {
> uri += "/";
> }
> uri += "main.wsdl";
> response.sendRedirect(uri);
> return;
> }
>
> It seems, that ServiceMix redirects (302) user to mail.wsdl page which
> doesn't exists in my configuration. So, how to configure well HTTP consumer
> endpoint to allow wsdl responding?
The redirect is just fine. Usually a 404 indicates that the SU is
misconfigured somehow. Can you post the xbean.xml for the
servicemix-http SU as well as the WSDL for the servicemix-jsr181 SU?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/