Re[3]: http component - parsing error

[Ilya Kuleshov <ik...@naumen.ru>]

Hi, Guillaume!

As  to  my  question about overlapping paths. I found that it does not
matter  what  endpointUrl  you  choose  when sending the soap message,
because  http-component  inspects  the  wsa:To  header  and routes the
message  to  the right endpoint. This seems strange to me but there is
nothing bad about it so I'm satisfied entirely. :)

GN>> I have just add a fix.
GN>> Now, when trying to start multiple endpoints with overlapping pathes (as
GN>> you were trying to do)
GN>> a more explicit exception is thrown.

IK> And what's wrong in overlapping pathes? I anticipated to be able to have
IK> several services bound to a single path. That's why we need wsa:To
IK> routing  here.  If  I  make a distinct path for each service then each
IK> time  I'd like to query a particular service I should send my messages
IK> to a different url? At least it worked for me until recent update, so
IK> I thought this is a normal behaviour for http-component.

GN>> Btw, not sure what you are trying to do.
GN>> The wsa:ReplyTo is not implemented yet. What would you expect it to do ?

IK> nothing, I just copied it from the http-component's tests before
IK> sending you a report in order to be sure that I don't miss some
IK> intricate magic. For now I just need the wsa:To routing.

Re: http component - parsing error

[Guillaume Nodet <gu...@worldonline.fr>]

Ilya Kuleshov wrote:

>Hi, Guillaume!
>
>As  to  my  question about overlapping paths. I found that it does not
>matter  what  endpointUrl  you  choose  when sending the soap message,
>because  http-component  inspects  the  wsa:To  header  and routes the
>message  to  the right endpoint. This seems strange to me but there is
>nothing bad about it so I'm satisfied entirely. :)
>  
>
Exactly :)

Guillaume Nodet