You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Michael Mattox <mi...@gmail.com> on 2007/05/29 18:23:35 UTC
404 Unable to find requested resource when requesting WSDL
Help!
I set up an http consumer & provider to pass through to an external
webservice running under tomcat. I cannot for the life of me get it
to work. Searching the mailing list shows the same error reported by
other people but I do not find any solutions posted. I'm using
3.1.1-incubating.
xbean.xml:
<http:endpoint service="test:MyProviderService"
endpoint="myProvider"
role="provider"
soapVersion="1.1"
soap="true"
locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
/>
<http:endpoint service="test:MyConsumerService"
endpoint="myConsumer"
targetService="test:MyProviderService"
role="consumer"
locationURI="http://0.0.0.0:8192/BookService/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true"
/>
web page result (http://ics030126:8192/BookService/?wsdl):
HTTP ERROR: 404
Unable to find requested resource
RequestURI=/BookService/main.wsdl
Powered by Jetty://
in the servicemix log:
18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
0.0.0.0:8192 | JettyContextManager |
ntextManager$ThreadPoolWrapper 441 | Dispatching job:
HEP@2923429[d=true,io=0,w=true,b=0|0]
18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
/BookService/?wsdl HTTP/1.1
Host: ics030126:8192
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
0.0.0.0:8192 | JettyContextManager |
ntextManager$ThreadPoolWrapper 441 | Dispatching job:
HEP@2923429[d=true,io=1,w=true,b=0|0]
18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
/BookService/main.wsdl HTTP/1.1
Host: ics030126:8192
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
definition
18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
icemix.common.DefaultComponent 79 | Querying service description for
ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
icemix.common.DefaultComponent 87 | No description found for
{http://servicemix.apache.org/service}MyProviderService:myProvider
I'm completely blocked by this, quite embarrassingly so in front of my
client! If anyone can tell me how to get past this I'd be very
grateful. I'm trying to build a proof of concept for a new project.
Thanks,
Michael
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
> Though the jbi.xml descriptor in the standard doesn't seem to inhibit
> several endpoints in one service unit, your setup with establishing 2
> endpoints in one xbean seems a bit inusual.
Why is that so? I thought it would be unusual to create a new SU for
each endpoint.
What is really strange is my coworker put together a demo that does
something similar but with some BPEL inside and it worked for him
several months ago (3.1-SNAPSHOT). And he can't figure out why mine
isn't working, especially since I used his project as an example.
> Have you tried to establish the same thing with 2 different service
> units?
I create a new SU and then put the consumer in one and the provider in
the other. I think this is when I got a 302 when I called my web
service with SOAP-UI but I don't remember for sure. I can live
without the WSDL but I need the SOAP call to work.
I then deleted my entire project and started again from scratch. I
got the same result.
> Have you tried to name the endpoints differently, but let the target
> endpoint of the consumer unit point to the endpoint of the provider?
> > > > <http:endpoint ...
> > > > endpoint="BookServiceHttpPort"
> > > > <http:endpoint ...
> > > > endpoint="bookServiceConsumerEndpoint"
> > > ...
> > > > targetEndpoint="BookServiceHttpPort"
I don't understand this, that's what I had.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
FINALLY! It works! Thank you & everyone else for all the help, I
really appreciate it.
On 6/1/07, Bummer <sa...@gmail.com> wrote:
>
> Try take out the "/" character in your http-provider xbean setting at
> locationURI ...
> It should work (SOAPUI request and response)
>
>
> Michael Mattox-3 wrote:
> >
> > To help those who may have the same problem and hopefully stumble upon
> > this thread in the archives, here is the xbean.xml that allows
> > retrieving the WSDL :
> >
> > <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> > xmlns:echange="http://www.company.com/echange"
> > xmlns:xfire="http://xfire.codehaus.org">
> >
> > <http:endpoint service="xfire:EchoService"
> > endpoint="EchoServiceHttpBinding"
> > targetService="xfire:EchoService"
> > soapVersion="1.1"
> > soap="true"
> > role="consumer"
> > locationURI="http://localhost:9000/EchoService"
> > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> >
> > wsdlResource="http://localhost:8080/test-business-service/services/EchoService?wsdl"
> > />
> >
> > <http:endpoint service="xfire:EchoService"
> > endpoint="EchoServiceHttpBindingProvider"
> > soapVersion="1.1"
> > soap="true"
> > role="provider"
> >
> > locationURI="http://localhost:8080/test-business-service/services/EchoService/"
> >
> > wsdlResource="http://localhost:8080/test-business-service/services/EchoService?wsdl"/>
> >
> > </beans>
> >
> > URL: http://localhost:9000/EchoService/?wsdl
> >
> >
>
> --
> View this message in context: http://www.nabble.com/404-Unable-to-find-requested-resource-when-requesting-WSDL-tf3835016s12049.html#a10904449
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Bummer <sa...@gmail.com>.
Try take out the "/" character in your http-provider xbean setting at
locationURI ...
It should work (SOAPUI request and response)
Michael Mattox-3 wrote:
>
> To help those who may have the same problem and hopefully stumble upon
> this thread in the archives, here is the xbean.xml that allows
> retrieving the WSDL :
>
> <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:echange="http://www.company.com/echange"
> xmlns:xfire="http://xfire.codehaus.org">
>
> <http:endpoint service="xfire:EchoService"
> endpoint="EchoServiceHttpBinding"
> targetService="xfire:EchoService"
> soapVersion="1.1"
> soap="true"
> role="consumer"
> locationURI="http://localhost:9000/EchoService"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>
> wsdlResource="http://localhost:8080/test-business-service/services/EchoService?wsdl"
> />
>
> <http:endpoint service="xfire:EchoService"
> endpoint="EchoServiceHttpBindingProvider"
> soapVersion="1.1"
> soap="true"
> role="provider"
>
> locationURI="http://localhost:8080/test-business-service/services/EchoService/"
>
> wsdlResource="http://localhost:8080/test-business-service/services/EchoService?wsdl"/>
>
> </beans>
>
> URL: http://localhost:9000/EchoService/?wsdl
>
>
--
View this message in context: http://www.nabble.com/404-Unable-to-find-requested-resource-when-requesting-WSDL-tf3835016s12049.html#a10904449
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
To help those who may have the same problem and hopefully stumble upon
this thread in the archives, here is the xbean.xml that allows
retrieving the WSDL :
<beans xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:echange="http://www.company.com/echange"
xmlns:xfire="http://xfire.codehaus.org">
<http:endpoint service="xfire:EchoService"
endpoint="EchoServiceHttpBinding"
targetService="xfire:EchoService"
soapVersion="1.1"
soap="true"
role="consumer"
locationURI="http://localhost:9000/EchoService"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
wsdlResource="http://localhost:8080/test-business-service/services/EchoService?wsdl"
/>
<http:endpoint service="xfire:EchoService"
endpoint="EchoServiceHttpBindingProvider"
soapVersion="1.1"
soap="true"
role="provider"
locationURI="http://localhost:8080/test-business-service/services/EchoService/"
wsdlResource="http://localhost:8080/test-business-service/services/EchoService?wsdl"/>
</beans>
URL: http://localhost:9000/EchoService/?wsdl
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
Ok, I finally got my WSDL to show up! I'm not sure what changed
exactly but I thought maybe it was my web service so I created an
EchoService with a singe echo method.
Only thing is when I call the service I get a parsing error:
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,39]
Message: expected start or end tag
at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader.nextTag(Extend
edXMLStreamReader.java:54)
at org.apache.servicemix.soap.marshalers.SoapReader.readSoapUsingStax(So
apReader.java:164)
at org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java
:89)
at org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java
:76)
at org.apache.servicemix.http.processors.ProviderProcessor.process(Provi
derProcessor.java:174)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLi
feCycle.java:489)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(Async
BaseLifeCycle.java:441)
at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLife
Cycle.java:46)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun
d(DeliveryChannelImpl.java:595)
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
w.java:174)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j
ava:176)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav
a:134)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
ker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
ker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
I'm not sure if I'm doing something wrong again or if this is a bug. Any ideas?
Thanks to everyone for the help. I think I'm almost there!
RE: 404 Unable to find requested resource when requesting WSDL
Posted by "Rossmanith, Philipp" <ph...@t-systems.es>.
Though the jbi.xml descriptor in the standard doesn't seem to inhibit
several endpoints in one service unit, your setup with establishing 2
endpoints in one xbean seems a bit inusual.
Have you tried to establish the same thing with 2 different service
units?
> > > > > > > <loc-message>More than one endpoint found in the SU for
key:
> > > > > > > {http://xfire.codeh
> > > > > > > aus.org}BookService:bookServiceEndpoint</loc-message>
Have you tried to name the endpoints differently, but let the target
endpoint of the consumer unit point to the endpoint of the provider?
> > > <http:endpoint ...
> > > endpoint="BookServiceHttpPort"
> > > <http:endpoint ...
> > > endpoint="bookServiceConsumerEndpoint"
> > ...
> > > targetEndpoint="BookServiceHttpPort"
Ciao,
Philipp
> -----Mensaje original-----
> De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> Enviado el: jueves, 31 de mayo de 2007 13:06
> Para: servicemix-users@geronimo.apache.org
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> > Well, you're still using different endpoint names.
> >
> > > <http:endpoint ...
> > > endpoint="BookServiceHttpPort"
> > > <http:endpoint ...
> > > endpoint="bookServiceConsumerEndpoint"
> > ...
> > > targetEndpoint="bookServiceProviderEndpoint"
>
> If I use the same name I get the parsing error and my SA won't start.
>
> > I don't have code for your particular example, but take a look at
this:
> > Provider:
> > <jsr181:endpoint
> > endpoint="SensorDataServiceSOAPPort"
> > .../>
>
> I think the difference is your example uses jsr181 and I'm using http.
>
> Thanks
> Michael
This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
> Well, you're still using different endpoint names.
>
> > <http:endpoint ...
> > endpoint="BookServiceHttpPort"
> > <http:endpoint ...
> > endpoint="bookServiceConsumerEndpoint"
> ...
> > targetEndpoint="bookServiceProviderEndpoint"
If I use the same name I get the parsing error and my SA won't start.
> I don't have code for your particular example, but take a look at this:
> Provider:
> <jsr181:endpoint
> endpoint="SensorDataServiceSOAPPort"
> .../>
I think the difference is your example uses jsr181 and I'm using http.
Thanks
Michael
RE: 404 Unable to find requested resource when requesting WSDL
Posted by "Rossmanith, Philipp" <ph...@t-systems.es>.
Well, you're still using different endpoint names.
> <http:endpoint ...
> endpoint="BookServiceHttpPort"
> <http:endpoint ...
> endpoint="bookServiceConsumerEndpoint"
...
> targetEndpoint="bookServiceProviderEndpoint"
I don't have code for your particular example, but take a look at this:
Consumer:
>>
<http:endpoint service="tsys:SensorDataService"
endpoint="SensorDataServiceSOAPPort"
role="consumer"
.../>
<<
Provider:
>>
<jsr181:endpoint
endpoint="SensorDataServiceSOAPPort"
.../>
<<
In MC4J, this gives me *one* endpoint with a name {http___...}SensorDataServiceSensorDataServiceSOAPPort with 2 sub types, internal and external.
Hope this helps,
Ciao,
Philipp
> -----Mensaje original-----
> De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> Enviado el: miércoles, 30 de mayo de 2007 19:20
> Para: servicemix-users@geronimo.apache.org
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> Changed it to:
>
> <http:endpoint service="test:BookService"
> endpoint="BookServiceHttpPort"
> role="provider"
> soapVersion="1.1"
> soap="true"
> locationURI="http://127.0.0.1:8080/test-business-
> service/services/BookService"
> />
>
> <http:endpoint service="test:BookService"
> endpoint="bookServiceConsumerEndpoint"
> targetService="test:BookService"
> targetEndpoint="bookServiceProviderEndpoint"
> role="consumer"
> locationURI="http://0.0.0.0:8192/BookService/"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> soapVersion="1.1"
> soap="true"
> />
>
>
> I get the same error as before.
>
> What is weird is a friend has used servicemix to do this and he spent
> yesterday afternoon with me and he couldn't figure it out either.
>
>
> On 5/30/07, Rossmanith, Philipp <ph...@t-systems.es> wrote:
> >
> > No worries. The name of the endpoint attribute in your xbean.xml; try
> setting it to the name of the port.
> >
> > Please note that endpoint is a WSDL 2.0 term, whereas your WSDL is 1.1.
> >
> > Ciao,
> > Philipp
> >
> > > -----Mensaje original-----
> > > De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> > > Enviado el: miércoles, 30 de mayo de 2007 17:56
> > > Para: servicemix-users@geronimo.apache.org
> > > Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> > > Importancia: Baja
> > >
> > > Philipp,
> > >
> > > Try setting what to the name of the port? (sorry I'm new at this)
> > >
> > > Thanks,
> > > Michael
> > >
> > > On 5/30/07, Rossmanith, Philipp <ph...@t-systems.es>
> wrote:
> > > >
> > > > Hi Michael,
> > > >
> > > > Try setting it to the name of the port: BookServiceHttpPort.
> > > >
> > > > Have you tried making the Web service accessible via ServiceMix
> without
> > > establishing a consumer endpoint for it?
> > > >
> > > > If so, was it visible via JMX?
> > > >
> > > > Ciao,
> > > > Philipp
> > > >
> > > > > -----Mensaje original-----
> > > > > De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> > > > > Enviado el: miércoles, 30 de mayo de 2007 17:41
> > > > > Para: servicemix-users@geronimo.apache.org
> > > > > Asunto: Re: 404 Unable to find requested resource when requesting
> WSDL
> > > > > Importancia: Baja
> > > > >
> > > > > I just searched the WSDL and do not find the word "endpoint" at
> all.
> > > > > I am attaching the WSDL.
> > > > >
> > > > > I get the same result:
> > > > >
> > > > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > > > e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
> > > > > definition
> > > > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > > > icemix.common.DefaultComponent 79 | Querying service description
> for
> > > > >
> > >
> ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bo
> > > > > okServiceProviderEndpoint]
> > > > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > > > icemix.common.DefaultComponent 87 | No description found for
> > > > > {http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
> > > > >
> > > > > This tells me that servicemix is making the connection from the
> > > > > consumer to the provider, and that it cannot locate the provider.
> > > > > Which I don't understand because it's in the xbean.xml, pasted
> again
> > > > > here for reference:
> > > > >
> > > > > <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> > > > > xmlns:test="http://xfire.codehaus.org">
> > > > >
> > > > > <http:endpoint service="test:BookService"
> > > > > endpoint="bookServiceProviderEndpoint"
> > > > > role="provider"
> > > > > soapVersion="1.1"
> > > > > soap="true"
> > > > > locationURI="http://127.0.0.1:8080/test-business-
> > > > > service/services/BookService"
> > > > > />
> > > > >
> > > > > <!--
> > > > > targetService="test:BookService"
> > > > > -->
> > > > >
> > > > > <http:endpoint service="test:BookService"
> > > > > endpoint="bookServiceConsumerEndpoint"
> > > > > targetService="test:BookService"
> > > > > targetEndpoint="bookServiceProviderEndpoint"
> > > > > role="consumer"
> > > > > locationURI="http://0.0.0.0:8192/BookService/"
> > > > > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> > > > > soapVersion="1.1"
> > > > > soap="true"
> > > > > />
> > > > >
> > > > >
> > > > > </beans>
> > > > >
> > > > >
> > > > > On 5/30/07, Gert Vanthienen <ge...@skynet.be> wrote:
> > > > > > Michael,
> > > > > >
> > > > > > Isn't it possible that the webservice you're targeting is also
> > > called
> > > > > > bookServiceEndpoint? If not, can you try to revert to different
> > > > > > endpoint names and add a targetService and targetEndpoint
> attribute
> > > to
> > > > > > your consumer end?
> > > > > >
> > > > > > Gert
> > > > > >
> > > > > > Michael Mattox wrote:
> > > > > > >> I haven't tried your particular setup yet, but from my
> experience
> > > > > both
> > > > > > >> the service and the endpoint names need to match between a
> > > consumer
> > > > > > >> and a provider.
> > > > > > >> > endpoint="providerBookService"
> > > > > > >> > endpoint="consumerBookService"
> > > > > > >>
> > > > > > >> Hope that helps.
> > > > > > >
> > > > > > > Philipp, thanks for the suggestion. I just set the two
> endpoints
> > > to
> > > > > > > "bookServiceEndpoint" and I get this error:
> > > > > > >
> > > > > > > <loc-message>More than one endpoint found in the SU for key:
> > > > > > > {http://xfire.codeh
> > > > > > > aus.org}BookService:bookServiceEndpoint</loc-message>
> > > > > > >
> > > > > > > -Michael
> > > > > > >
> > > > > >
> > > >
> > > > This e-mail may contain confidential or privileged information. Any
> > > unauthorised
> > > > copying, use or distribution of this information is strictly
> prohibited.
> > > >
> >
> > This e-mail may contain confidential or privileged information. Any
> unauthorised
> > copying, use or distribution of this information is strictly prohibited.
> >
This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
Changed it to:
<http:endpoint service="test:BookService"
endpoint="BookServiceHttpPort"
role="provider"
soapVersion="1.1"
soap="true"
locationURI="http://127.0.0.1:8080/test-business-service/services/BookService"
/>
<http:endpoint service="test:BookService"
endpoint="bookServiceConsumerEndpoint"
targetService="test:BookService"
targetEndpoint="bookServiceProviderEndpoint"
role="consumer"
locationURI="http://0.0.0.0:8192/BookService/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true"
/>
I get the same error as before.
What is weird is a friend has used servicemix to do this and he spent
yesterday afternoon with me and he couldn't figure it out either.
On 5/30/07, Rossmanith, Philipp <ph...@t-systems.es> wrote:
>
> No worries. The name of the endpoint attribute in your xbean.xml; try setting it to the name of the port.
>
> Please note that endpoint is a WSDL 2.0 term, whereas your WSDL is 1.1.
>
> Ciao,
> Philipp
>
> > -----Mensaje original-----
> > De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> > Enviado el: miércoles, 30 de mayo de 2007 17:56
> > Para: servicemix-users@geronimo.apache.org
> > Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> > Importancia: Baja
> >
> > Philipp,
> >
> > Try setting what to the name of the port? (sorry I'm new at this)
> >
> > Thanks,
> > Michael
> >
> > On 5/30/07, Rossmanith, Philipp <ph...@t-systems.es> wrote:
> > >
> > > Hi Michael,
> > >
> > > Try setting it to the name of the port: BookServiceHttpPort.
> > >
> > > Have you tried making the Web service accessible via ServiceMix without
> > establishing a consumer endpoint for it?
> > >
> > > If so, was it visible via JMX?
> > >
> > > Ciao,
> > > Philipp
> > >
> > > > -----Mensaje original-----
> > > > De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> > > > Enviado el: miércoles, 30 de mayo de 2007 17:41
> > > > Para: servicemix-users@geronimo.apache.org
> > > > Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> > > > Importancia: Baja
> > > >
> > > > I just searched the WSDL and do not find the word "endpoint" at all.
> > > > I am attaching the WSDL.
> > > >
> > > > I get the same result:
> > > >
> > > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > > e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
> > > > definition
> > > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > > icemix.common.DefaultComponent 79 | Querying service description for
> > > >
> > ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bo
> > > > okServiceProviderEndpoint]
> > > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > > icemix.common.DefaultComponent 87 | No description found for
> > > > {http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
> > > >
> > > > This tells me that servicemix is making the connection from the
> > > > consumer to the provider, and that it cannot locate the provider.
> > > > Which I don't understand because it's in the xbean.xml, pasted again
> > > > here for reference:
> > > >
> > > > <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> > > > xmlns:test="http://xfire.codehaus.org">
> > > >
> > > > <http:endpoint service="test:BookService"
> > > > endpoint="bookServiceProviderEndpoint"
> > > > role="provider"
> > > > soapVersion="1.1"
> > > > soap="true"
> > > > locationURI="http://127.0.0.1:8080/test-business-
> > > > service/services/BookService"
> > > > />
> > > >
> > > > <!--
> > > > targetService="test:BookService"
> > > > -->
> > > >
> > > > <http:endpoint service="test:BookService"
> > > > endpoint="bookServiceConsumerEndpoint"
> > > > targetService="test:BookService"
> > > > targetEndpoint="bookServiceProviderEndpoint"
> > > > role="consumer"
> > > > locationURI="http://0.0.0.0:8192/BookService/"
> > > > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> > > > soapVersion="1.1"
> > > > soap="true"
> > > > />
> > > >
> > > >
> > > > </beans>
> > > >
> > > >
> > > > On 5/30/07, Gert Vanthienen <ge...@skynet.be> wrote:
> > > > > Michael,
> > > > >
> > > > > Isn't it possible that the webservice you're targeting is also
> > called
> > > > > bookServiceEndpoint? If not, can you try to revert to different
> > > > > endpoint names and add a targetService and targetEndpoint attribute
> > to
> > > > > your consumer end?
> > > > >
> > > > > Gert
> > > > >
> > > > > Michael Mattox wrote:
> > > > > >> I haven't tried your particular setup yet, but from my experience
> > > > both
> > > > > >> the service and the endpoint names need to match between a
> > consumer
> > > > > >> and a provider.
> > > > > >> > endpoint="providerBookService"
> > > > > >> > endpoint="consumerBookService"
> > > > > >>
> > > > > >> Hope that helps.
> > > > > >
> > > > > > Philipp, thanks for the suggestion. I just set the two endpoints
> > to
> > > > > > "bookServiceEndpoint" and I get this error:
> > > > > >
> > > > > > <loc-message>More than one endpoint found in the SU for key:
> > > > > > {http://xfire.codeh
> > > > > > aus.org}BookService:bookServiceEndpoint</loc-message>
> > > > > >
> > > > > > -Michael
> > > > > >
> > > > >
> > >
> > > This e-mail may contain confidential or privileged information. Any
> > unauthorised
> > > copying, use or distribution of this information is strictly prohibited.
> > >
>
> This e-mail may contain confidential or privileged information. Any unauthorised
> copying, use or distribution of this information is strictly prohibited.
>
RE: 404 Unable to find requested resource when requesting WSDL
Posted by "Rossmanith, Philipp" <ph...@t-systems.es>.
No worries. The name of the endpoint attribute in your xbean.xml; try setting it to the name of the port.
Please note that endpoint is a WSDL 2.0 term, whereas your WSDL is 1.1.
Ciao,
Philipp
> -----Mensaje original-----
> De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> Enviado el: miércoles, 30 de mayo de 2007 17:56
> Para: servicemix-users@geronimo.apache.org
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> Philipp,
>
> Try setting what to the name of the port? (sorry I'm new at this)
>
> Thanks,
> Michael
>
> On 5/30/07, Rossmanith, Philipp <ph...@t-systems.es> wrote:
> >
> > Hi Michael,
> >
> > Try setting it to the name of the port: BookServiceHttpPort.
> >
> > Have you tried making the Web service accessible via ServiceMix without
> establishing a consumer endpoint for it?
> >
> > If so, was it visible via JMX?
> >
> > Ciao,
> > Philipp
> >
> > > -----Mensaje original-----
> > > De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> > > Enviado el: miércoles, 30 de mayo de 2007 17:41
> > > Para: servicemix-users@geronimo.apache.org
> > > Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> > > Importancia: Baja
> > >
> > > I just searched the WSDL and do not find the word "endpoint" at all.
> > > I am attaching the WSDL.
> > >
> > > I get the same result:
> > >
> > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
> > > definition
> > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > icemix.common.DefaultComponent 79 | Querying service description for
> > >
> ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bo
> > > okServiceProviderEndpoint]
> > > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > > icemix.common.DefaultComponent 87 | No description found for
> > > {http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
> > >
> > > This tells me that servicemix is making the connection from the
> > > consumer to the provider, and that it cannot locate the provider.
> > > Which I don't understand because it's in the xbean.xml, pasted again
> > > here for reference:
> > >
> > > <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> > > xmlns:test="http://xfire.codehaus.org">
> > >
> > > <http:endpoint service="test:BookService"
> > > endpoint="bookServiceProviderEndpoint"
> > > role="provider"
> > > soapVersion="1.1"
> > > soap="true"
> > > locationURI="http://127.0.0.1:8080/test-business-
> > > service/services/BookService"
> > > />
> > >
> > > <!--
> > > targetService="test:BookService"
> > > -->
> > >
> > > <http:endpoint service="test:BookService"
> > > endpoint="bookServiceConsumerEndpoint"
> > > targetService="test:BookService"
> > > targetEndpoint="bookServiceProviderEndpoint"
> > > role="consumer"
> > > locationURI="http://0.0.0.0:8192/BookService/"
> > > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> > > soapVersion="1.1"
> > > soap="true"
> > > />
> > >
> > >
> > > </beans>
> > >
> > >
> > > On 5/30/07, Gert Vanthienen <ge...@skynet.be> wrote:
> > > > Michael,
> > > >
> > > > Isn't it possible that the webservice you're targeting is also
> called
> > > > bookServiceEndpoint? If not, can you try to revert to different
> > > > endpoint names and add a targetService and targetEndpoint attribute
> to
> > > > your consumer end?
> > > >
> > > > Gert
> > > >
> > > > Michael Mattox wrote:
> > > > >> I haven't tried your particular setup yet, but from my experience
> > > both
> > > > >> the service and the endpoint names need to match between a
> consumer
> > > > >> and a provider.
> > > > >> > endpoint="providerBookService"
> > > > >> > endpoint="consumerBookService"
> > > > >>
> > > > >> Hope that helps.
> > > > >
> > > > > Philipp, thanks for the suggestion. I just set the two endpoints
> to
> > > > > "bookServiceEndpoint" and I get this error:
> > > > >
> > > > > <loc-message>More than one endpoint found in the SU for key:
> > > > > {http://xfire.codeh
> > > > > aus.org}BookService:bookServiceEndpoint</loc-message>
> > > > >
> > > > > -Michael
> > > > >
> > > >
> >
> > This e-mail may contain confidential or privileged information. Any
> unauthorised
> > copying, use or distribution of this information is strictly prohibited.
> >
This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
Philipp,
Try setting what to the name of the port? (sorry I'm new at this)
Thanks,
Michael
On 5/30/07, Rossmanith, Philipp <ph...@t-systems.es> wrote:
>
> Hi Michael,
>
> Try setting it to the name of the port: BookServiceHttpPort.
>
> Have you tried making the Web service accessible via ServiceMix without establishing a consumer endpoint for it?
>
> If so, was it visible via JMX?
>
> Ciao,
> Philipp
>
> > -----Mensaje original-----
> > De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> > Enviado el: miércoles, 30 de mayo de 2007 17:41
> > Para: servicemix-users@geronimo.apache.org
> > Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> > Importancia: Baja
> >
> > I just searched the WSDL and do not find the word "endpoint" at all.
> > I am attaching the WSDL.
> >
> > I get the same result:
> >
> > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
> > definition
> > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > icemix.common.DefaultComponent 79 | Querying service description for
> > ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bo
> > okServiceProviderEndpoint]
> > 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> > icemix.common.DefaultComponent 87 | No description found for
> > {http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
> >
> > This tells me that servicemix is making the connection from the
> > consumer to the provider, and that it cannot locate the provider.
> > Which I don't understand because it's in the xbean.xml, pasted again
> > here for reference:
> >
> > <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> > xmlns:test="http://xfire.codehaus.org">
> >
> > <http:endpoint service="test:BookService"
> > endpoint="bookServiceProviderEndpoint"
> > role="provider"
> > soapVersion="1.1"
> > soap="true"
> > locationURI="http://127.0.0.1:8080/test-business-
> > service/services/BookService"
> > />
> >
> > <!--
> > targetService="test:BookService"
> > -->
> >
> > <http:endpoint service="test:BookService"
> > endpoint="bookServiceConsumerEndpoint"
> > targetService="test:BookService"
> > targetEndpoint="bookServiceProviderEndpoint"
> > role="consumer"
> > locationURI="http://0.0.0.0:8192/BookService/"
> > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> > soapVersion="1.1"
> > soap="true"
> > />
> >
> >
> > </beans>
> >
> >
> > On 5/30/07, Gert Vanthienen <ge...@skynet.be> wrote:
> > > Michael,
> > >
> > > Isn't it possible that the webservice you're targeting is also called
> > > bookServiceEndpoint? If not, can you try to revert to different
> > > endpoint names and add a targetService and targetEndpoint attribute to
> > > your consumer end?
> > >
> > > Gert
> > >
> > > Michael Mattox wrote:
> > > >> I haven't tried your particular setup yet, but from my experience
> > both
> > > >> the service and the endpoint names need to match between a consumer
> > > >> and a provider.
> > > >> > endpoint="providerBookService"
> > > >> > endpoint="consumerBookService"
> > > >>
> > > >> Hope that helps.
> > > >
> > > > Philipp, thanks for the suggestion. I just set the two endpoints to
> > > > "bookServiceEndpoint" and I get this error:
> > > >
> > > > <loc-message>More than one endpoint found in the SU for key:
> > > > {http://xfire.codeh
> > > > aus.org}BookService:bookServiceEndpoint</loc-message>
> > > >
> > > > -Michael
> > > >
> > >
>
> This e-mail may contain confidential or privileged information. Any unauthorised
> copying, use or distribution of this information is strictly prohibited.
>
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
> Have you tried making the Web service accessible via ServiceMix without establishing a consumer endpoint for it?
>
> If so, was it visible via JMX?
I'm not sure how useful this is, I commented out the consumer
definition in the xbean.xml, in jconsole I see the endpoint but there
is no selector running and therefore no connection possible on port
8192.
Before commenting out the consumer, both endpoints were present in JMX.
I'm not sure why but in tree panel, the name has {http____xfire...
I'm not sure why the ____, it should be {http://xfire... i'm
wondering if this is why servicemix can't find the provider. it's
being registered with a different name. Some kind of substitution on
the ://
RE: 404 Unable to find requested resource when requesting WSDL
Posted by "Rossmanith, Philipp" <ph...@t-systems.es>.
Hi Michael,
Try setting it to the name of the port: BookServiceHttpPort.
Have you tried making the Web service accessible via ServiceMix without establishing a consumer endpoint for it?
If so, was it visible via JMX?
Ciao,
Philipp
> -----Mensaje original-----
> De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> Enviado el: miércoles, 30 de mayo de 2007 17:41
> Para: servicemix-users@geronimo.apache.org
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> I just searched the WSDL and do not find the word "endpoint" at all.
> I am attaching the WSDL.
>
> I get the same result:
>
> 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
> definition
> 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> icemix.common.DefaultComponent 79 | Querying service description for
> ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bo
> okServiceProviderEndpoint]
> 17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
> icemix.common.DefaultComponent 87 | No description found for
> {http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
>
> This tells me that servicemix is making the connection from the
> consumer to the provider, and that it cannot locate the provider.
> Which I don't understand because it's in the xbean.xml, pasted again
> here for reference:
>
> <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:test="http://xfire.codehaus.org">
>
> <http:endpoint service="test:BookService"
> endpoint="bookServiceProviderEndpoint"
> role="provider"
> soapVersion="1.1"
> soap="true"
> locationURI="http://127.0.0.1:8080/test-business-
> service/services/BookService"
> />
>
> <!--
> targetService="test:BookService"
> -->
>
> <http:endpoint service="test:BookService"
> endpoint="bookServiceConsumerEndpoint"
> targetService="test:BookService"
> targetEndpoint="bookServiceProviderEndpoint"
> role="consumer"
> locationURI="http://0.0.0.0:8192/BookService/"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> soapVersion="1.1"
> soap="true"
> />
>
>
> </beans>
>
>
> On 5/30/07, Gert Vanthienen <ge...@skynet.be> wrote:
> > Michael,
> >
> > Isn't it possible that the webservice you're targeting is also called
> > bookServiceEndpoint? If not, can you try to revert to different
> > endpoint names and add a targetService and targetEndpoint attribute to
> > your consumer end?
> >
> > Gert
> >
> > Michael Mattox wrote:
> > >> I haven't tried your particular setup yet, but from my experience
> both
> > >> the service and the endpoint names need to match between a consumer
> > >> and a provider.
> > >> > endpoint="providerBookService"
> > >> > endpoint="consumerBookService"
> > >>
> > >> Hope that helps.
> > >
> > > Philipp, thanks for the suggestion. I just set the two endpoints to
> > > "bookServiceEndpoint" and I get this error:
> > >
> > > <loc-message>More than one endpoint found in the SU for key:
> > > {http://xfire.codeh
> > > aus.org}BookService:bookServiceEndpoint</loc-message>
> > >
> > > -Michael
> > >
> >
This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
I just searched the WSDL and do not find the word "endpoint" at all.
I am attaching the WSDL.
I get the same result:
17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
definition
17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
icemix.common.DefaultComponent 79 | Querying service description for
ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bookServiceProviderEndpoint]
17:38:15,998 | DEBUG | btpool0-1 | HttpComponent |
icemix.common.DefaultComponent 87 | No description found for
{http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
This tells me that servicemix is making the connection from the
consumer to the provider, and that it cannot locate the provider.
Which I don't understand because it's in the xbean.xml, pasted again
here for reference:
<beans xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:test="http://xfire.codehaus.org">
<http:endpoint service="test:BookService"
endpoint="bookServiceProviderEndpoint"
role="provider"
soapVersion="1.1"
soap="true"
locationURI="http://127.0.0.1:8080/test-business-service/services/BookService"
/>
<!--
targetService="test:BookService"
-->
<http:endpoint service="test:BookService"
endpoint="bookServiceConsumerEndpoint"
targetService="test:BookService"
targetEndpoint="bookServiceProviderEndpoint"
role="consumer"
locationURI="http://0.0.0.0:8192/BookService/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true"
/>
</beans>
On 5/30/07, Gert Vanthienen <ge...@skynet.be> wrote:
> Michael,
>
> Isn't it possible that the webservice you're targeting is also called
> bookServiceEndpoint? If not, can you try to revert to different
> endpoint names and add a targetService and targetEndpoint attribute to
> your consumer end?
>
> Gert
>
> Michael Mattox wrote:
> >> I haven't tried your particular setup yet, but from my experience both
> >> the service and the endpoint names need to match between a consumer
> >> and a provider.
> >> > endpoint="providerBookService"
> >> > endpoint="consumerBookService"
> >>
> >> Hope that helps.
> >
> > Philipp, thanks for the suggestion. I just set the two endpoints to
> > "bookServiceEndpoint" and I get this error:
> >
> > <loc-message>More than one endpoint found in the SU for key:
> > {http://xfire.codeh
> > aus.org}BookService:bookServiceEndpoint</loc-message>
> >
> > -Michael
> >
>
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Gert Vanthienen <ge...@skynet.be>.
Michael,
Isn't it possible that the webservice you're targeting is also called
bookServiceEndpoint? If not, can you try to revert to different
endpoint names and add a targetService and targetEndpoint attribute to
your consumer end?
Gert
Michael Mattox wrote:
>> I haven't tried your particular setup yet, but from my experience both
>> the service and the endpoint names need to match between a consumer
>> and a provider.
>> > endpoint="providerBookService"
>> > endpoint="consumerBookService"
>>
>> Hope that helps.
>
> Philipp, thanks for the suggestion. I just set the two endpoints to
> "bookServiceEndpoint" and I get this error:
>
> <loc-message>More than one endpoint found in the SU for key:
> {http://xfire.codeh
> aus.org}BookService:bookServiceEndpoint</loc-message>
>
> -Michael
>
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
> I haven't tried your particular setup yet, but from my experience both the service and the endpoint names need to match between a consumer and a provider.
> > endpoint="providerBookService"
> > endpoint="consumerBookService"
>
> Hope that helps.
Philipp, thanks for the suggestion. I just set the two endpoints to
"bookServiceEndpoint" and I get this error:
<loc-message>More than one endpoint found in the SU for key: {http://xfire.codeh
aus.org}BookService:bookServiceEndpoint</loc-message>
-Michael
RE: 404 Unable to find requested resource when requesting WSDL
Posted by "Rossmanith, Philipp" <ph...@t-systems.es>.
Hi Michael,
I haven't tried your particular setup yet, but from my experience both the service and the endpoint names need to match between a consumer and a provider.
> endpoint="providerBookService"
> endpoint="consumerBookService"
Hope that helps.
Ciao,
Philipp
> -----Mensaje original-----
> De: Michael Mattox [mailto:michaelmaillist@gmail.com]
> Enviado el: miércoles, 30 de mayo de 2007 10:43
> Para: servicemix-users@geronimo.apache.org
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> > Michael,
> >
> > One possible problem is the service name of your HTTP provider endpoint,
> > which should match the name of the external web service you want to
> > call. You can also use the same name on your consumer endpoint to
> > obtain the pass-through behavior you describe, there's no need to use
> > the targetService attribute there.
> >
> > I also think that you have to specify a real IP address or hostname.
> > You can use the 0.0.0.0 on a consumer endpoint to specify that you want
> > to bind to all networks your host is in, but here you'll have to specify
> > localhost or 127.0.0.1.
>
> Thanks for your suggestions. I'm still not having any luck. I
> updated my xbean.xml to use the same namespace as the WSDL and the
> service name to be the same as the service name in the WSDL:
>
> <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:test="http://xfire.codehaus.org/BookService">
>
> <http:endpoint service="test:BookService"
> endpoint="providerBookService"
> role="provider"
> soapVersion="1.1"
> soap="true"
> locationURI="http://127.0.0.1:8080/test-business-
> service/services/BookService"
> />
>
> <http:endpoint service="test:BookService"
> endpoint="consumerBookService"
> role="consumer"
> locationURI="http://0.0.0.0:8192/BookService/"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> soapVersion="1.1"
> soap="true"
> targetService="test:BookService"
> />
>
> I get exactly the same error. I tried naming the endpoints the same
> but I get an error on startup. I tried removing targetService as
> well. Nothing is working for me, it's quite frustrating. I had a
> coworker helping me yesterday, he has already used servicemix and he
> couldn't figure out my problem either.
>
> If you have any more ideas please let me know. This use case is so
> simple, I think it'd be good to include it with the examples.
>
> -Michael
This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.
Orchestration using jsr-181 - Not able to understand fully
Posted by mr...@wipro.com.
Hello,
I am trying to work out the example given in
http://incubator.apache.org/servicemix/orchestration-with-jsr181.html
for the programmatic orchestration with the jsr-181.
However - what I am not understanding is how the orchestration logic
will work for a real-time invocation. (For testing purposes - it looks
like they are using a hard coded response.xml for the zip and a new Date
for getting time). I am not seeing actual invocation of the web
services.
Can someone give me the entire code snippet how it would work in real
time invocation? Or I am in the wrong direction ?
Regards,
Mrudula
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
> Michael,
>
> One possible problem is the service name of your HTTP provider endpoint,
> which should match the name of the external web service you want to
> call. You can also use the same name on your consumer endpoint to
> obtain the pass-through behavior you describe, there's no need to use
> the targetService attribute there.
>
> I also think that you have to specify a real IP address or hostname.
> You can use the 0.0.0.0 on a consumer endpoint to specify that you want
> to bind to all networks your host is in, but here you'll have to specify
> localhost or 127.0.0.1.
Thanks for your suggestions. I'm still not having any luck. I
updated my xbean.xml to use the same namespace as the WSDL and the
service name to be the same as the service name in the WSDL:
<beans xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:test="http://xfire.codehaus.org/BookService">
<http:endpoint service="test:BookService"
endpoint="providerBookService"
role="provider"
soapVersion="1.1"
soap="true"
locationURI="http://127.0.0.1:8080/test-business-service/services/BookService"
/>
<http:endpoint service="test:BookService"
endpoint="consumerBookService"
role="consumer"
locationURI="http://0.0.0.0:8192/BookService/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true"
targetService="test:BookService"
/>
I get exactly the same error. I tried naming the endpoints the same
but I get an error on startup. I tried removing targetService as
well. Nothing is working for me, it's quite frustrating. I had a
coworker helping me yesterday, he has already used servicemix and he
couldn't figure out my problem either.
If you have any more ideas please let me know. This use case is so
simple, I think it'd be good to include it with the examples.
-Michael
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Michael Mattox <mi...@gmail.com>.
> I tried with SOAP-UI and sent soap request to my
> http-consumer(http://localhost:8192/HttpService)
> and it worked.. It gave me the corrent soap response.
I just installed SOAP-UI and using the servicemix endpoint does not
work for me. I don't get any errors, and this is the only thing I see
in the log:
11:30:55,698 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
0.0.0.0:8192 | JettyContextManager |
ntextManager$ThreadPoolWrapper 441 | Dispatching job:
HEP@1745182[d=true,io=0,w=true,b=0|0]
I'm totally stuck. I have no choice but to try either Petals or Mule
for my client demo (I'm way past due).
I created a JIRA issue:
https://issues.apache.org/activemq/browse/SM-961
-Michael
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Bummer <sa...@gmail.com>.
I am having the same(?) problem.
0) I have a external webservice (w/ tomcat+axis2).
<wsdl:definitions
targetNamespace="http://axis2.demo.shanframework.org"....>
<wsdl:service name="StockQuoteService">
1) In http-consumer/provider setting
<beans xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:axis2="http://axis2.demo.shanframework.org"
xmlns:jsr181test="http://servicemix.apache.org/samples/jsr181test">
<http:endpoint
service="axis2:StockQuoteService"
endpoint="callerendpoint"
role="provider"
locationURI="http://localhost:8080/axis2/services/StockQuoteService"
wsdlResource="http://localhost:8080/axis2/services/StockQuoteService?wsdl"
soapVersion="1.1"
soap="true"
/>
<http:endpoint service="jsr181test:HttpService"
endpoint="HttpService"
targetService="axis2:StockQuoteService"
targetEndpoint="callerendpoint"
role="consumer"
locationURI="http://0.0.0.0:8192/HttpService/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true"
/>
</beans>
I tried with SOAP-UI and sent soap request to my
http-consumer(http://localhost:8192/HttpService)
and it worked.. It gave me the corrent soap response.
But I still get wsdl in either JMX console or Web browser. In web browser, I
tried the consumer-http
address which is "http://localhost:8192/HttpService/?wsdl and I didn't get
the wsdl.
In JMX, at the "MBeans->org.apache.servicemix->ServiceMix->Endpoint" node I
could see
the http-provider
({http___axis2.demo.shanframework.org}StockQuoteServicecallerendpoint) and
in that opertions, I clicked the "loadWSDL" and didn't gave me the WSDL.
Benamin wrote:
>
> Yes, I am using ServiceMix to host my web service, but I still wanted to
> use the http endpoints as a proof of concept thing. And yes, I can use
> SOAP UI to generate a request and send it through a browser and get my
> expected output. But the http provider fails with that error.
>
>
>
>
> Gert Vanthienen wrote:
>>
>> L.S.,
>>
>> The provider http:endpoint is used to make an external web service
>> available to the ESB. So, in your case, there should an up-and-running
>> web service on the url specified in the endpoint. Whether or not you
>> create this endpoint, the WSDL should always have been available on that
>> location beforehand. Have you tried invoking this webservice with e.g.
>> the Eclipse webservices client or SoapUI client?
>>
>> What confuses me, is the URL for your website, which suggests that
>> you've also build you webservice using ServiceMix (it might just be a
>> coincidence off course). If your service is already available in the
>> ESB, there is no need to go through the HTTP endpoints to invoke it...
>>
>> Gert
>>
>>
>> Benamin wrote:
>>> So, if you had a wsdl with the following namespace and service:
>>>
>>> <wsdl:definitions targetNamespace="http://tapestry.cgi.com/smix">
>>> <wsdl:service name="NSRService">
>>>
>>> a valid http provider would be :
>>>
>>> <beans xmlns:http="http://servicemix.apache.org/http/1.0"
>>> xmlns:sm="http://tapestry.cgi.com/smix">
>>>
>>> <http:endpoint service="sm:NSRService"
>>> endpoint="myProvider"
>>> role="provider"
>>> locationURI="http://localhost:8192/NSRService/"
>>> soap="true"
>>> />
>>>
>>> I can browse this wsdl at http://localhost:8192/NSRService/main.wsdl as
>>> expected.
>>>
>>> Yet, I get error with the following. Any ideas?
>>>
>>> ERROR - HttpComponent - Error processing exchange
>>> InOut[
>>> id: ID:massive-64941-1180471881454-11:0
>>> status: Active
>>> role: provider
>>> service: {http://tapestry.cgi.com/smix}NSRService
>>> endpoint: myProvider
>>> in: <?xml version="1.0" encoding="UTF-8"?><hello>Testing</hello>
>>> ]
>>> org.apache.commons.httpclient.NoHttpResponseException: The server
>>> localhost
>>> failed to respond
>>> at
>>> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1835)
>>> at
>>> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
>>> at
>>> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
>>> at
>>> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
>>> at
>>> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
>>> at
>>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
>>> at
>>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
>>> at
>>> org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:168)
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>>> at
>>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>>> at
>>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>>> at
>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>>> at
>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>>> at java.lang.Thread.run(Thread.java:595)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Gert Vanthienen wrote:
>>>> L.S.,
>>>>
>>>> The namespace should match the target namespace of your wsdl and the
>>>> service name should match the service defined in there as well.
>>>>
>>>> Gert
>>>>
>>>>
>>>> Benamin wrote:
>>>>> I may be having a similar problem. So in that particular http
>>>>> provider,
>>>>> the
>>>>> service should be
>>>>> service="test:BookService"
>>>>>
>>>>> ?
>>>>>
>>>>>
>>>>>
>>>>> Gert Vanthienen wrote:
>>>>>
>>>>>> Michael,
>>>>>>
>>>>>> One possible problem is the service name of your HTTP provider
>>>>>> endpoint,
>>>>>> which should match the name of the external web service you want to
>>>>>> call. You can also use the same name on your consumer endpoint to
>>>>>> obtain the pass-through behavior you describe, there's no need to use
>>>>>> the targetService attribute there.
>>>>>>
>>>>>> I also think that you have to specify a real IP address or hostname.
>>>>>> You can use the 0.0.0.0 on a consumer endpoint to specify that you
>>>>>> want
>>>>>> to bind to all networks your host is in, but here you'll have to
>>>>>> specify
>>>>>> localhost or 127.0.0.1.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Gert
>>>>>>
>>>>>> Michael Mattox wrote:
>>>>>>
>>>>>>> Help!
>>>>>>>
>>>>>>> I set up an http consumer & provider to pass through to an external
>>>>>>> webservice running under tomcat. I cannot for the life of me get it
>>>>>>> to work. Searching the mailing list shows the same error reported
>>>>>>> by
>>>>>>> other people but I do not find any solutions posted. I'm using
>>>>>>> 3.1.1-incubating.
>>>>>>>
>>>>>>> xbean.xml:
>>>>>>>
>>>>>>> <http:endpoint service="test:MyProviderService"
>>>>>>> endpoint="myProvider"
>>>>>>> role="provider"
>>>>>>> soapVersion="1.1"
>>>>>>> soap="true"
>>>>>>>
>>>>>>> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>>>>>>>
>>>>>>> />
>>>>>>>
>>>>>>> <http:endpoint service="test:MyConsumerService"
>>>>>>> endpoint="myConsumer"
>>>>>>> targetService="test:MyProviderService"
>>>>>>> role="consumer"
>>>>>>> locationURI="http://0.0.0.0:8192/BookService/"
>>>>>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>>>>>>> soapVersion="1.1"
>>>>>>> soap="true"
>>>>>>> />
>>>>>>>
>>>>>>> web page result (http://ics030126:8192/BookService/?wsdl):
>>>>>>>
>>>>>>> HTTP ERROR: 404
>>>>>>>
>>>>>>> Unable to find requested resource
>>>>>>>
>>>>>>> RequestURI=/BookService/main.wsdl
>>>>>>>
>>>>>>> Powered by Jetty://
>>>>>>>
>>>>>>> in the servicemix log:
>>>>>>>
>>>>>>> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector
>>>>>>> @
>>>>>>> 0.0.0.0:8192 | JettyContextManager |
>>>>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>>>>> HEP@2923429[d=true,io=0,w=true,b=0|0]
>>>>>>> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>>>>> /BookService/?wsdl HTTP/1.1
>>>>>>> Host: ics030126:8192
>>>>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>>>>> Accept:
>>>>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>>>>
>>>>>>> Accept-Language: en-us,en;q=0.5
>>>>>>> Accept-Encoding: gzip,deflate
>>>>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>>>>> Keep-Alive: 300
>>>>>>> Connection: keep-alive
>>>>>>>
>>>>>>>
>>>>>>> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector
>>>>>>> @
>>>>>>> 0.0.0.0:8192 | JettyContextManager |
>>>>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>>>>> HEP@2923429[d=true,io=1,w=true,b=0|0]
>>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>>>>> /BookService/main.wsdl HTTP/1.1
>>>>>>> Host: ics030126:8192
>>>>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>>>>> Accept:
>>>>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>>>>
>>>>>>> Accept-Language: en-us,en;q=0.5
>>>>>>> Accept-Encoding: gzip,deflate
>>>>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>>>>> Keep-Alive: 300
>>>>>>> Connection: keep-alive
>>>>>>>
>>>>>>>
>>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>>>> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
>>>>>>> definition
>>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>>>> icemix.common.DefaultComponent 79 | Querying service description
>>>>>>> for
>>>>>>> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>>>>>>>
>>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>>>> icemix.common.DefaultComponent 87 | No description found for
>>>>>>> {http://servicemix.apache.org/service}MyProviderService:myProvider
>>>>>>>
>>>>>>>
>>>>>>> I'm completely blocked by this, quite embarrassingly so in front of
>>>>>>> my
>>>>>>> client! If anyone can tell me how to get past this I'd be very
>>>>>>> grateful. I'm trying to build a proof of concept for a new project.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Michael
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/404-Unable-to-find-requested-resource-when-requesting-WSDL-tf3835016s12049.html#a10885256
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Benamin <be...@bisonline.com>.
Yes, I am using ServiceMix to host my web service, but I still wanted to use
the http endpoints as a proof of concept thing. And yes, I can use SOAP UI
to generate a request and send it through a browser and get my expected
output. But the http provider fails with that error.
Gert Vanthienen wrote:
>
> L.S.,
>
> The provider http:endpoint is used to make an external web service
> available to the ESB. So, in your case, there should an up-and-running
> web service on the url specified in the endpoint. Whether or not you
> create this endpoint, the WSDL should always have been available on that
> location beforehand. Have you tried invoking this webservice with e.g.
> the Eclipse webservices client or SoapUI client?
>
> What confuses me, is the URL for your website, which suggests that
> you've also build you webservice using ServiceMix (it might just be a
> coincidence off course). If your service is already available in the
> ESB, there is no need to go through the HTTP endpoints to invoke it...
>
> Gert
>
>
> Benamin wrote:
>> So, if you had a wsdl with the following namespace and service:
>>
>> <wsdl:definitions targetNamespace="http://tapestry.cgi.com/smix">
>> <wsdl:service name="NSRService">
>>
>> a valid http provider would be :
>>
>> <beans xmlns:http="http://servicemix.apache.org/http/1.0"
>> xmlns:sm="http://tapestry.cgi.com/smix">
>>
>> <http:endpoint service="sm:NSRService"
>> endpoint="myProvider"
>> role="provider"
>> locationURI="http://localhost:8192/NSRService/"
>> soap="true"
>> />
>>
>> I can browse this wsdl at http://localhost:8192/NSRService/main.wsdl as
>> expected.
>>
>> Yet, I get error with the following. Any ideas?
>>
>> ERROR - HttpComponent - Error processing exchange InOut[
>> id: ID:massive-64941-1180471881454-11:0
>> status: Active
>> role: provider
>> service: {http://tapestry.cgi.com/smix}NSRService
>> endpoint: myProvider
>> in: <?xml version="1.0" encoding="UTF-8"?><hello>Testing</hello>
>> ]
>> org.apache.commons.httpclient.NoHttpResponseException: The server
>> localhost
>> failed to respond
>> at
>> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1835)
>> at
>> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
>> at
>> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
>> at
>> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
>> at
>> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
>> at
>> org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:168)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>> at
>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>> at
>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>> at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>> at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>> at java.lang.Thread.run(Thread.java:595)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Gert Vanthienen wrote:
>>> L.S.,
>>>
>>> The namespace should match the target namespace of your wsdl and the
>>> service name should match the service defined in there as well.
>>>
>>> Gert
>>>
>>>
>>> Benamin wrote:
>>>> I may be having a similar problem. So in that particular http
>>>> provider,
>>>> the
>>>> service should be
>>>> service="test:BookService"
>>>>
>>>> ?
>>>>
>>>>
>>>>
>>>> Gert Vanthienen wrote:
>>>>
>>>>> Michael,
>>>>>
>>>>> One possible problem is the service name of your HTTP provider
>>>>> endpoint,
>>>>> which should match the name of the external web service you want to
>>>>> call. You can also use the same name on your consumer endpoint to
>>>>> obtain the pass-through behavior you describe, there's no need to use
>>>>> the targetService attribute there.
>>>>>
>>>>> I also think that you have to specify a real IP address or hostname.
>>>>> You can use the 0.0.0.0 on a consumer endpoint to specify that you
>>>>> want
>>>>> to bind to all networks your host is in, but here you'll have to
>>>>> specify
>>>>> localhost or 127.0.0.1.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Gert
>>>>>
>>>>> Michael Mattox wrote:
>>>>>
>>>>>> Help!
>>>>>>
>>>>>> I set up an http consumer & provider to pass through to an external
>>>>>> webservice running under tomcat. I cannot for the life of me get it
>>>>>> to work. Searching the mailing list shows the same error reported by
>>>>>> other people but I do not find any solutions posted. I'm using
>>>>>> 3.1.1-incubating.
>>>>>>
>>>>>> xbean.xml:
>>>>>>
>>>>>> <http:endpoint service="test:MyProviderService"
>>>>>> endpoint="myProvider"
>>>>>> role="provider"
>>>>>> soapVersion="1.1"
>>>>>> soap="true"
>>>>>>
>>>>>> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>>>>>>
>>>>>> />
>>>>>>
>>>>>> <http:endpoint service="test:MyConsumerService"
>>>>>> endpoint="myConsumer"
>>>>>> targetService="test:MyProviderService"
>>>>>> role="consumer"
>>>>>> locationURI="http://0.0.0.0:8192/BookService/"
>>>>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>>>>>> soapVersion="1.1"
>>>>>> soap="true"
>>>>>> />
>>>>>>
>>>>>> web page result (http://ics030126:8192/BookService/?wsdl):
>>>>>>
>>>>>> HTTP ERROR: 404
>>>>>>
>>>>>> Unable to find requested resource
>>>>>>
>>>>>> RequestURI=/BookService/main.wsdl
>>>>>>
>>>>>> Powered by Jetty://
>>>>>>
>>>>>> in the servicemix log:
>>>>>>
>>>>>> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>>>>> 0.0.0.0:8192 | JettyContextManager |
>>>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>>>> HEP@2923429[d=true,io=0,w=true,b=0|0]
>>>>>> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>>>> /BookService/?wsdl HTTP/1.1
>>>>>> Host: ics030126:8192
>>>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>>>> Accept:
>>>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>>>
>>>>>> Accept-Language: en-us,en;q=0.5
>>>>>> Accept-Encoding: gzip,deflate
>>>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>>>> Keep-Alive: 300
>>>>>> Connection: keep-alive
>>>>>>
>>>>>>
>>>>>> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>>>>> 0.0.0.0:8192 | JettyContextManager |
>>>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>>>> HEP@2923429[d=true,io=1,w=true,b=0|0]
>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>>>> /BookService/main.wsdl HTTP/1.1
>>>>>> Host: ics030126:8192
>>>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>>>> Accept:
>>>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>>>
>>>>>> Accept-Language: en-us,en;q=0.5
>>>>>> Accept-Encoding: gzip,deflate
>>>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>>>> Keep-Alive: 300
>>>>>> Connection: keep-alive
>>>>>>
>>>>>>
>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>>> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
>>>>>> definition
>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>>> icemix.common.DefaultComponent 79 | Querying service description
>>>>>> for
>>>>>> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>>>>>>
>>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>>> icemix.common.DefaultComponent 87 | No description found for
>>>>>> {http://servicemix.apache.org/service}MyProviderService:myProvider
>>>>>>
>>>>>>
>>>>>> I'm completely blocked by this, quite embarrassingly so in front of
>>>>>> my
>>>>>> client! If anyone can tell me how to get past this I'd be very
>>>>>> grateful. I'm trying to build a proof of concept for a new project.
>>>>>>
>>>>>> Thanks,
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
--
View this message in context: http://www.nabble.com/404-Unable-to-find-requested-resource-when-requesting-WSDL-tf3835016s12049.html#a10874927
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
The provider http:endpoint is used to make an external web service
available to the ESB. So, in your case, there should an up-and-running
web service on the url specified in the endpoint. Whether or not you
create this endpoint, the WSDL should always have been available on that
location beforehand. Have you tried invoking this webservice with e.g.
the Eclipse webservices client or SoapUI client?
What confuses me, is the URL for your website, which suggests that
you've also build you webservice using ServiceMix (it might just be a
coincidence off course). If your service is already available in the
ESB, there is no need to go through the HTTP endpoints to invoke it...
Gert
Benamin wrote:
> So, if you had a wsdl with the following namespace and service:
>
> <wsdl:definitions targetNamespace="http://tapestry.cgi.com/smix">
> <wsdl:service name="NSRService">
>
> a valid http provider would be :
>
> <beans xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:sm="http://tapestry.cgi.com/smix">
>
> <http:endpoint service="sm:NSRService"
> endpoint="myProvider"
> role="provider"
> locationURI="http://localhost:8192/NSRService/"
> soap="true"
> />
>
> I can browse this wsdl at http://localhost:8192/NSRService/main.wsdl as
> expected.
>
> Yet, I get error with the following. Any ideas?
>
> ERROR - HttpComponent - Error processing exchange InOut[
> id: ID:massive-64941-1180471881454-11:0
> status: Active
> role: provider
> service: {http://tapestry.cgi.com/smix}NSRService
> endpoint: myProvider
> in: <?xml version="1.0" encoding="UTF-8"?><hello>Testing</hello>
> ]
> org.apache.commons.httpclient.NoHttpResponseException: The server localhost
> failed to respond
> at
> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1835)
> at
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
> at
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
> at
> org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:168)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
>
>
>
>
>
>
>
>
>
> Gert Vanthienen wrote:
>> L.S.,
>>
>> The namespace should match the target namespace of your wsdl and the
>> service name should match the service defined in there as well.
>>
>> Gert
>>
>>
>> Benamin wrote:
>>> I may be having a similar problem. So in that particular http provider,
>>> the
>>> service should be
>>> service="test:BookService"
>>>
>>> ?
>>>
>>>
>>>
>>> Gert Vanthienen wrote:
>>>
>>>> Michael,
>>>>
>>>> One possible problem is the service name of your HTTP provider endpoint,
>>>> which should match the name of the external web service you want to
>>>> call. You can also use the same name on your consumer endpoint to
>>>> obtain the pass-through behavior you describe, there's no need to use
>>>> the targetService attribute there.
>>>>
>>>> I also think that you have to specify a real IP address or hostname.
>>>> You can use the 0.0.0.0 on a consumer endpoint to specify that you want
>>>> to bind to all networks your host is in, but here you'll have to specify
>>>> localhost or 127.0.0.1.
>>>>
>>>> Regards,
>>>>
>>>> Gert
>>>>
>>>> Michael Mattox wrote:
>>>>
>>>>> Help!
>>>>>
>>>>> I set up an http consumer & provider to pass through to an external
>>>>> webservice running under tomcat. I cannot for the life of me get it
>>>>> to work. Searching the mailing list shows the same error reported by
>>>>> other people but I do not find any solutions posted. I'm using
>>>>> 3.1.1-incubating.
>>>>>
>>>>> xbean.xml:
>>>>>
>>>>> <http:endpoint service="test:MyProviderService"
>>>>> endpoint="myProvider"
>>>>> role="provider"
>>>>> soapVersion="1.1"
>>>>> soap="true"
>>>>>
>>>>> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>>>>>
>>>>> />
>>>>>
>>>>> <http:endpoint service="test:MyConsumerService"
>>>>> endpoint="myConsumer"
>>>>> targetService="test:MyProviderService"
>>>>> role="consumer"
>>>>> locationURI="http://0.0.0.0:8192/BookService/"
>>>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>>>>> soapVersion="1.1"
>>>>> soap="true"
>>>>> />
>>>>>
>>>>> web page result (http://ics030126:8192/BookService/?wsdl):
>>>>>
>>>>> HTTP ERROR: 404
>>>>>
>>>>> Unable to find requested resource
>>>>>
>>>>> RequestURI=/BookService/main.wsdl
>>>>>
>>>>> Powered by Jetty://
>>>>>
>>>>> in the servicemix log:
>>>>>
>>>>> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>>>> 0.0.0.0:8192 | JettyContextManager |
>>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>>> HEP@2923429[d=true,io=0,w=true,b=0|0]
>>>>> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>>> /BookService/?wsdl HTTP/1.1
>>>>> Host: ics030126:8192
>>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>>> Accept:
>>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>>
>>>>> Accept-Language: en-us,en;q=0.5
>>>>> Accept-Encoding: gzip,deflate
>>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>>> Keep-Alive: 300
>>>>> Connection: keep-alive
>>>>>
>>>>>
>>>>> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>>>> 0.0.0.0:8192 | JettyContextManager |
>>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>>> HEP@2923429[d=true,io=1,w=true,b=0|0]
>>>>> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>>> /BookService/main.wsdl HTTP/1.1
>>>>> Host: ics030126:8192
>>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>>> Accept:
>>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>>
>>>>> Accept-Language: en-us,en;q=0.5
>>>>> Accept-Encoding: gzip,deflate
>>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>>> Keep-Alive: 300
>>>>> Connection: keep-alive
>>>>>
>>>>>
>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
>>>>> definition
>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>> icemix.common.DefaultComponent 79 | Querying service description for
>>>>> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>>>>>
>>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>>> icemix.common.DefaultComponent 87 | No description found for
>>>>> {http://servicemix.apache.org/service}MyProviderService:myProvider
>>>>>
>>>>>
>>>>> I'm completely blocked by this, quite embarrassingly so in front of my
>>>>> client! If anyone can tell me how to get past this I'd be very
>>>>> grateful. I'm trying to build a proof of concept for a new project.
>>>>>
>>>>> Thanks,
>>>>> Michael
>>>>>
>>>>>
>>>>
>>>
>>
>>
>
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Benamin <be...@bisonline.com>.
So, if you had a wsdl with the following namespace and service:
<wsdl:definitions targetNamespace="http://tapestry.cgi.com/smix">
<wsdl:service name="NSRService">
a valid http provider would be :
<beans xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:sm="http://tapestry.cgi.com/smix">
<http:endpoint service="sm:NSRService"
endpoint="myProvider"
role="provider"
locationURI="http://localhost:8192/NSRService/"
soap="true"
/>
I can browse this wsdl at http://localhost:8192/NSRService/main.wsdl as
expected.
Yet, I get error with the following. Any ideas?
ERROR - HttpComponent - Error processing exchange InOut[
id: ID:massive-64941-1180471881454-11:0
status: Active
role: provider
service: {http://tapestry.cgi.com/smix}NSRService
endpoint: myProvider
in: <?xml version="1.0" encoding="UTF-8"?><hello>Testing</hello>
]
org.apache.commons.httpclient.NoHttpResponseException: The server localhost
failed to respond
at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1835)
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:168)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Gert Vanthienen wrote:
>
> L.S.,
>
> The namespace should match the target namespace of your wsdl and the
> service name should match the service defined in there as well.
>
> Gert
>
>
> Benamin wrote:
>> I may be having a similar problem. So in that particular http provider,
>> the
>> service should be
>> service="test:BookService"
>>
>> ?
>>
>>
>>
>> Gert Vanthienen wrote:
>>
>>> Michael,
>>>
>>> One possible problem is the service name of your HTTP provider endpoint,
>>> which should match the name of the external web service you want to
>>> call. You can also use the same name on your consumer endpoint to
>>> obtain the pass-through behavior you describe, there's no need to use
>>> the targetService attribute there.
>>>
>>> I also think that you have to specify a real IP address or hostname.
>>> You can use the 0.0.0.0 on a consumer endpoint to specify that you want
>>> to bind to all networks your host is in, but here you'll have to specify
>>> localhost or 127.0.0.1.
>>>
>>> Regards,
>>>
>>> Gert
>>>
>>> Michael Mattox wrote:
>>>
>>>> Help!
>>>>
>>>> I set up an http consumer & provider to pass through to an external
>>>> webservice running under tomcat. I cannot for the life of me get it
>>>> to work. Searching the mailing list shows the same error reported by
>>>> other people but I do not find any solutions posted. I'm using
>>>> 3.1.1-incubating.
>>>>
>>>> xbean.xml:
>>>>
>>>> <http:endpoint service="test:MyProviderService"
>>>> endpoint="myProvider"
>>>> role="provider"
>>>> soapVersion="1.1"
>>>> soap="true"
>>>>
>>>> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>>>>
>>>> />
>>>>
>>>> <http:endpoint service="test:MyConsumerService"
>>>> endpoint="myConsumer"
>>>> targetService="test:MyProviderService"
>>>> role="consumer"
>>>> locationURI="http://0.0.0.0:8192/BookService/"
>>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>>>> soapVersion="1.1"
>>>> soap="true"
>>>> />
>>>>
>>>> web page result (http://ics030126:8192/BookService/?wsdl):
>>>>
>>>> HTTP ERROR: 404
>>>>
>>>> Unable to find requested resource
>>>>
>>>> RequestURI=/BookService/main.wsdl
>>>>
>>>> Powered by Jetty://
>>>>
>>>> in the servicemix log:
>>>>
>>>> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>>> 0.0.0.0:8192 | JettyContextManager |
>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>> HEP@2923429[d=true,io=0,w=true,b=0|0]
>>>> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>> /BookService/?wsdl HTTP/1.1
>>>> Host: ics030126:8192
>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>> Accept:
>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>
>>>> Accept-Language: en-us,en;q=0.5
>>>> Accept-Encoding: gzip,deflate
>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>> Keep-Alive: 300
>>>> Connection: keep-alive
>>>>
>>>>
>>>> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>>> 0.0.0.0:8192 | JettyContextManager |
>>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>>> HEP@2923429[d=true,io=1,w=true,b=0|0]
>>>> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
>>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>>> /BookService/main.wsdl HTTP/1.1
>>>> Host: ics030126:8192
>>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>>> Accept:
>>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>>
>>>> Accept-Language: en-us,en;q=0.5
>>>> Accept-Encoding: gzip,deflate
>>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>> Keep-Alive: 300
>>>> Connection: keep-alive
>>>>
>>>>
>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
>>>> definition
>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>> icemix.common.DefaultComponent 79 | Querying service description for
>>>> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>>>>
>>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>>> icemix.common.DefaultComponent 87 | No description found for
>>>> {http://servicemix.apache.org/service}MyProviderService:myProvider
>>>>
>>>>
>>>> I'm completely blocked by this, quite embarrassingly so in front of my
>>>> client! If anyone can tell me how to get past this I'd be very
>>>> grateful. I'm trying to build a proof of concept for a new project.
>>>>
>>>> Thanks,
>>>> Michael
>>>>
>>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/404-Unable-to-find-requested-resource-when-requesting-WSDL-tf3835016s12049.html#a10862479
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
The namespace should match the target namespace of your wsdl and the
service name should match the service defined in there as well.
Gert
Benamin wrote:
> I may be having a similar problem. So in that particular http provider, the
> service should be
> service="test:BookService"
>
> ?
>
>
>
> Gert Vanthienen wrote:
>
>> Michael,
>>
>> One possible problem is the service name of your HTTP provider endpoint,
>> which should match the name of the external web service you want to
>> call. You can also use the same name on your consumer endpoint to
>> obtain the pass-through behavior you describe, there's no need to use
>> the targetService attribute there.
>>
>> I also think that you have to specify a real IP address or hostname.
>> You can use the 0.0.0.0 on a consumer endpoint to specify that you want
>> to bind to all networks your host is in, but here you'll have to specify
>> localhost or 127.0.0.1.
>>
>> Regards,
>>
>> Gert
>>
>> Michael Mattox wrote:
>>
>>> Help!
>>>
>>> I set up an http consumer & provider to pass through to an external
>>> webservice running under tomcat. I cannot for the life of me get it
>>> to work. Searching the mailing list shows the same error reported by
>>> other people but I do not find any solutions posted. I'm using
>>> 3.1.1-incubating.
>>>
>>> xbean.xml:
>>>
>>> <http:endpoint service="test:MyProviderService"
>>> endpoint="myProvider"
>>> role="provider"
>>> soapVersion="1.1"
>>> soap="true"
>>>
>>> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>>>
>>> />
>>>
>>> <http:endpoint service="test:MyConsumerService"
>>> endpoint="myConsumer"
>>> targetService="test:MyProviderService"
>>> role="consumer"
>>> locationURI="http://0.0.0.0:8192/BookService/"
>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>>> soapVersion="1.1"
>>> soap="true"
>>> />
>>>
>>> web page result (http://ics030126:8192/BookService/?wsdl):
>>>
>>> HTTP ERROR: 404
>>>
>>> Unable to find requested resource
>>>
>>> RequestURI=/BookService/main.wsdl
>>>
>>> Powered by Jetty://
>>>
>>> in the servicemix log:
>>>
>>> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>> 0.0.0.0:8192 | JettyContextManager |
>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>> HEP@2923429[d=true,io=0,w=true,b=0|0]
>>> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>> /BookService/?wsdl HTTP/1.1
>>> Host: ics030126:8192
>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>> Accept:
>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>
>>> Accept-Language: en-us,en;q=0.5
>>> Accept-Encoding: gzip,deflate
>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>> Keep-Alive: 300
>>> Connection: keep-alive
>>>
>>>
>>> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>>> 0.0.0.0:8192 | JettyContextManager |
>>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>>> HEP@2923429[d=true,io=1,w=true,b=0|0]
>>> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
>>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>>> /BookService/main.wsdl HTTP/1.1
>>> Host: ics030126:8192
>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>>> Accept:
>>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>
>>> Accept-Language: en-us,en;q=0.5
>>> Accept-Encoding: gzip,deflate
>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>> Keep-Alive: 300
>>> Connection: keep-alive
>>>
>>>
>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
>>> definition
>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>> icemix.common.DefaultComponent 79 | Querying service description for
>>> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>>>
>>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>>> icemix.common.DefaultComponent 87 | No description found for
>>> {http://servicemix.apache.org/service}MyProviderService:myProvider
>>>
>>>
>>> I'm completely blocked by this, quite embarrassingly so in front of my
>>> client! If anyone can tell me how to get past this I'd be very
>>> grateful. I'm trying to build a proof of concept for a new project.
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>
>
>
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Benamin <be...@bisonline.com>.
I may be having a similar problem. So in that particular http provider, the
service should be
service="test:BookService"
?
Gert Vanthienen wrote:
>
> Michael,
>
> One possible problem is the service name of your HTTP provider endpoint,
> which should match the name of the external web service you want to
> call. You can also use the same name on your consumer endpoint to
> obtain the pass-through behavior you describe, there's no need to use
> the targetService attribute there.
>
> I also think that you have to specify a real IP address or hostname.
> You can use the 0.0.0.0 on a consumer endpoint to specify that you want
> to bind to all networks your host is in, but here you'll have to specify
> localhost or 127.0.0.1.
>
> Regards,
>
> Gert
>
> Michael Mattox wrote:
>> Help!
>>
>> I set up an http consumer & provider to pass through to an external
>> webservice running under tomcat. I cannot for the life of me get it
>> to work. Searching the mailing list shows the same error reported by
>> other people but I do not find any solutions posted. I'm using
>> 3.1.1-incubating.
>>
>> xbean.xml:
>>
>> <http:endpoint service="test:MyProviderService"
>> endpoint="myProvider"
>> role="provider"
>> soapVersion="1.1"
>> soap="true"
>>
>> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>>
>> />
>>
>> <http:endpoint service="test:MyConsumerService"
>> endpoint="myConsumer"
>> targetService="test:MyProviderService"
>> role="consumer"
>> locationURI="http://0.0.0.0:8192/BookService/"
>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>> soapVersion="1.1"
>> soap="true"
>> />
>>
>> web page result (http://ics030126:8192/BookService/?wsdl):
>>
>> HTTP ERROR: 404
>>
>> Unable to find requested resource
>>
>> RequestURI=/BookService/main.wsdl
>>
>> Powered by Jetty://
>>
>> in the servicemix log:
>>
>> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>> 0.0.0.0:8192 | JettyContextManager |
>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>> HEP@2923429[d=true,io=0,w=true,b=0|0]
>> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>> /BookService/?wsdl HTTP/1.1
>> Host: ics030126:8192
>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>> Accept:
>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>
>> Accept-Language: en-us,en;q=0.5
>> Accept-Encoding: gzip,deflate
>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>> Keep-Alive: 300
>> Connection: keep-alive
>>
>>
>> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
>> 0.0.0.0:8192 | JettyContextManager |
>> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
>> HEP@2923429[d=true,io=1,w=true,b=0|0]
>> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
>> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
>> /BookService/main.wsdl HTTP/1.1
>> Host: ics030126:8192
>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
>> Accept:
>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>
>> Accept-Language: en-us,en;q=0.5
>> Accept-Encoding: gzip,deflate
>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>> Keep-Alive: 300
>> Connection: keep-alive
>>
>>
>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
>> definition
>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>> icemix.common.DefaultComponent 79 | Querying service description for
>> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>>
>> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
>> icemix.common.DefaultComponent 87 | No description found for
>> {http://servicemix.apache.org/service}MyProviderService:myProvider
>>
>>
>> I'm completely blocked by this, quite embarrassingly so in front of my
>> client! If anyone can tell me how to get past this I'd be very
>> grateful. I'm trying to build a proof of concept for a new project.
>>
>> Thanks,
>> Michael
>>
>
>
--
View this message in context: http://www.nabble.com/404-Unable-to-find-requested-resource-when-requesting-WSDL-tf3835016s12049.html#a10861135
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: 404 Unable to find requested resource when requesting WSDL
Posted by Gert Vanthienen <ge...@skynet.be>.
Michael,
One possible problem is the service name of your HTTP provider endpoint,
which should match the name of the external web service you want to
call. You can also use the same name on your consumer endpoint to
obtain the pass-through behavior you describe, there's no need to use
the targetService attribute there.
I also think that you have to specify a real IP address or hostname.
You can use the 0.0.0.0 on a consumer endpoint to specify that you want
to bind to all networks your host is in, but here you'll have to specify
localhost or 127.0.0.1.
Regards,
Gert
Michael Mattox wrote:
> Help!
>
> I set up an http consumer & provider to pass through to an external
> webservice running under tomcat. I cannot for the life of me get it
> to work. Searching the mailing list shows the same error reported by
> other people but I do not find any solutions posted. I'm using
> 3.1.1-incubating.
>
> xbean.xml:
>
> <http:endpoint service="test:MyProviderService"
> endpoint="myProvider"
> role="provider"
> soapVersion="1.1"
> soap="true"
>
> locationURI="http://0.0.0.0:8080/test-business-service/services/BookService"
>
> />
>
> <http:endpoint service="test:MyConsumerService"
> endpoint="myConsumer"
> targetService="test:MyProviderService"
> role="consumer"
> locationURI="http://0.0.0.0:8192/BookService/"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> soapVersion="1.1"
> soap="true"
> />
>
> web page result (http://ics030126:8192/BookService/?wsdl):
>
> HTTP ERROR: 404
>
> Unable to find requested resource
>
> RequestURI=/BookService/main.wsdl
>
> Powered by Jetty://
>
> in the servicemix log:
>
> 18:21:50,858 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
> 0.0.0.0:8192 | JettyContextManager |
> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
> HEP@2923429[d=true,io=0,w=true,b=0|0]
> 18:21:50,858 | DEBUG | btpool0-2 | ConsumerProcessor |
> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
> /BookService/?wsdl HTTP/1.1
> Host: ics030126:8192
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
> Accept:
> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
>
>
> 18:21:50,967 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @
> 0.0.0.0:8192 | JettyContextManager |
> ntextManager$ThreadPoolWrapper 441 | Dispatching job:
> HEP@2923429[d=true,io=1,w=true,b=0|0]
> 18:21:50,967 | DEBUG | btpool0-2 | ConsumerProcessor |
> p.processors.ConsumerProcessor 120 | Receiving HTTP request: GET
> /BookService/main.wsdl HTTP/1.1
> Host: ics030126:8192
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
> Accept:
> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
>
>
> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
> e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint
> definition
> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
> icemix.common.DefaultComponent 79 | Querying service description for
> ServiceEndpoint[service={http://servicemix.apache.org/service}MyProviderService,endpoint=myProvider]
>
> 18:21:50,967 | DEBUG | btpool0-2 | HttpComponent |
> icemix.common.DefaultComponent 87 | No description found for
> {http://servicemix.apache.org/service}MyProviderService:myProvider
>
>
> I'm completely blocked by this, quite embarrassingly so in front of my
> client! If anyone can tell me how to get past this I'd be very
> grateful. I'm trying to build a proof of concept for a new project.
>
> Thanks,
> Michael
>