You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Bernard Lupin <be...@yahoo.fr> on 2006/08/13 01:33:06 UTC
routing with servicemix-http
I've read all the posts "How to call a external webservice"
(http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and have
not found an answer to the problem I have :
In this configuration with servicemix-http and 2 http endpoints
client -> http endpoint consumer -> http endpoint provider -> external web
service, the message is well treated by the external WS but never returned
to the client. Is it a bug or a config problem ?
More generally speaking, I don't understand how routing works after the
chain below : how servicemix knows that the answered message should go from
http endpoint provider to http endpoint consumer and then to the client ?
I've read some posts about In messages or InOut messages. Where can I
configure such information ?
Thanks a lot.
Bernard
--
View this message in context: http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5780622
Sent from the ServiceMix - User forum at Nabble.com.
Re: routing with servicemix-http
Posted by Guillaume Nodet <gn...@gmail.com>.
Yes, but the choices are limited to the one supported by JBI which are
InOnly, RobustInOnly, InOptionalOut, InOut
On 8/17/06, Bernard Lupin <be...@yahoo.fr> wrote:
>
> Thank you Guillaume for the explanation. Could you confirm that this is
> configured with the "defaultMep" attribute ?
> And that the available choices are listed here :
> http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#patterns ?
> And that all these choices are available for servicemix-http and
> servicemix-jms components ?
> Regards,
> Bernard
>
>
> gnodet wrote:
> >
> > The InOut pattern contains the request and the exchange.
> > When a provider receives an InOut exchange, it has to fill the
> > "out" message and send the exchange back. The NMR will route
> > the exchange the the consumer component (the one who created
> > the exchange).
> > In this case, the http consumer endpoint will create
> > an InOut exchange when receiving an HTTP request, will send it to the
> > http provider endpoint. The http provider endpoint will send an HTTP
> > request
> > to the external web service, and when the http response comes, will create
> > the out message and send it back to the http consumer (who will fill the
> > HTTP response for the client).
> >
> > On 8/13/06, Bernard Lupin <be...@yahoo.fr> wrote:
> >>
> >>
> >> I've read all the posts "How to call a external webservice"
> >> (http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and have
> >> not found an answer to the problem I have :
> >> In this configuration with servicemix-http and 2 http endpoints
> >> client -> http endpoint consumer -> http endpoint provider -> external
> >> web
> >> service, the message is well treated by the external WS but never
> >> returned
> >> to the client. Is it a bug or a config problem ?
> >> More generally speaking, I don't understand how routing works after the
> >> chain below : how servicemix knows that the answered message should go
> >> from
> >> http endpoint provider to http endpoint consumer and then to the client ?
> >> I've read some posts about In messages or InOut messages. Where can I
> >> configure such information ?
> >> Thanks a lot.
> >> Bernard
> >> --
> >> View this message in context:
> >> http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5780622
> >> Sent from the ServiceMix - User forum at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> >
>
> --
> View this message in context: http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5842079
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: routing with servicemix-http
Posted by Bernard Lupin <be...@yahoo.fr>.
Thank you Guillaume for the explanation. Could you confirm that this is
configured with the "defaultMep" attribute ?
And that the available choices are listed here :
http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#patterns ?
And that all these choices are available for servicemix-http and
servicemix-jms components ?
Regards,
Bernard
gnodet wrote:
>
> The InOut pattern contains the request and the exchange.
> When a provider receives an InOut exchange, it has to fill the
> "out" message and send the exchange back. The NMR will route
> the exchange the the consumer component (the one who created
> the exchange).
> In this case, the http consumer endpoint will create
> an InOut exchange when receiving an HTTP request, will send it to the
> http provider endpoint. The http provider endpoint will send an HTTP
> request
> to the external web service, and when the http response comes, will create
> the out message and send it back to the http consumer (who will fill the
> HTTP response for the client).
>
> On 8/13/06, Bernard Lupin <be...@yahoo.fr> wrote:
>>
>>
>> I've read all the posts "How to call a external webservice"
>> (http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and have
>> not found an answer to the problem I have :
>> In this configuration with servicemix-http and 2 http endpoints
>> client -> http endpoint consumer -> http endpoint provider -> external
>> web
>> service, the message is well treated by the external WS but never
>> returned
>> to the client. Is it a bug or a config problem ?
>> More generally speaking, I don't understand how routing works after the
>> chain below : how servicemix knows that the answered message should go
>> from
>> http endpoint provider to http endpoint consumer and then to the client ?
>> I've read some posts about In messages or InOut messages. Where can I
>> configure such information ?
>> Thanks a lot.
>> Bernard
>> --
>> View this message in context:
>> http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5780622
>> Sent from the ServiceMix - User forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5842079
Sent from the ServiceMix - User forum at Nabble.com.
RE: routing with servicemix-http
Posted by Bernard Lupin <be...@yahoo.fr>.
Thank you for the advise. I suppose that the "trunk version" is the version
built from the sources with svn and maven. So I gave up with the 3.0-M2 and
built everything with the 3.0-SNAPSHOT and... it works !
Regards,
Bernard
I had the exactly same problem.
Guillaume Nodet solved it a few days ago. You must try the trunk version. I
think the problem was something around DeliveryChannel class.
Cheers,
João Vieira da Luz
--
View this message in context: http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5841771
Sent from the ServiceMix - User forum at Nabble.com.
RE: routing with servicemix-http
Posted by João Luz <jl...@sinfic.pt>.
I had the exactly same problem.
Guillaume Nodet solved it a few days ago. You must try the trunk version. I think the problem was something around DeliveryChannel class.
Cheers,
João Vieira da Luz
-----Original Message-----
From: Guillaume Nodet [mailto:gnodet@gmail.com]
Sent: domingo, 13 de Agosto de 2006 10:19
To: servicemix-users@geronimo.apache.org
Subject: Re: routing with servicemix-http
The InOut pattern contains the request and the exchange.
When a provider receives an InOut exchange, it has to fill the "out" message and send the exchange back. The NMR will route the exchange the the consumer component (the one who created the exchange).
In this case, the http consumer endpoint will create an InOut exchange when receiving an HTTP request, will send it to the http provider endpoint. The http provider endpoint will send an HTTP request to the external web service, and when the http response comes, will create the out message and send it back to the http consumer (who will fill the HTTP response for the client).
On 8/13/06, Bernard Lupin <be...@yahoo.fr> wrote:
>
>
> I've read all the posts "How to call a external webservice"
> (http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and
> have not found an answer to the problem I have :
> In this configuration with servicemix-http and 2 http endpoints client
> -> http endpoint consumer -> http endpoint provider -> external web
> service, the message is well treated by the external WS but never
> returned to the client. Is it a bug or a config problem ?
> More generally speaking, I don't understand how routing works after
> the chain below : how servicemix knows that the answered message
> should go from http endpoint provider to http endpoint consumer and
> then to the client ?
> I've read some posts about In messages or InOut messages. Where can I
> configure such information ?
> Thanks a lot.
> Bernard
> --
> View this message in context:
> http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a578
> 0622 Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: routing with servicemix-http
Posted by Guillaume Nodet <gn...@gmail.com>.
The InOut pattern contains the request and the exchange.
When a provider receives an InOut exchange, it has to fill the
"out" message and send the exchange back. The NMR will route
the exchange the the consumer component (the one who created
the exchange).
In this case, the http consumer endpoint will create
an InOut exchange when receiving an HTTP request, will send it to the
http provider endpoint. The http provider endpoint will send an HTTP request
to the external web service, and when the http response comes, will create
the out message and send it back to the http consumer (who will fill the
HTTP response for the client).
On 8/13/06, Bernard Lupin <be...@yahoo.fr> wrote:
>
>
> I've read all the posts "How to call a external webservice"
> (http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and have
> not found an answer to the problem I have :
> In this configuration with servicemix-http and 2 http endpoints
> client -> http endpoint consumer -> http endpoint provider -> external web
> service, the message is well treated by the external WS but never returned
> to the client. Is it a bug or a config problem ?
> More generally speaking, I don't understand how routing works after the
> chain below : how servicemix knows that the answered message should go
> from
> http endpoint provider to http endpoint consumer and then to the client ?
> I've read some posts about In messages or InOut messages. Where can I
> configure such information ?
> Thanks a lot.
> Bernard
> --
> View this message in context:
> http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5780622
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: routing with servicemix-http
Posted by Guillaume Nodet <gn...@gmail.com>.
Btw, the first thing to try is to put tcpmon or any other soap tool to
debug the HTTP request sent to the external web service and the
answer of this service.
On 8/13/06, Bernard Lupin <be...@yahoo.fr> wrote:
>
>
> I've read all the posts "How to call a external webservice"
> (http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and have
> not found an answer to the problem I have :
> In this configuration with servicemix-http and 2 http endpoints
> client -> http endpoint consumer -> http endpoint provider -> external web
> service, the message is well treated by the external WS but never returned
> to the client. Is it a bug or a config problem ?
> More generally speaking, I don't understand how routing works after the
> chain below : how servicemix knows that the answered message should go
> from
> http endpoint provider to http endpoint consumer and then to the client ?
> I've read some posts about In messages or InOut messages. Where can I
> configure such information ?
> Thanks a lot.
> Bernard
> --
> View this message in context:
> http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5780622
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet