Sorry, hit the button too early. So it should send it or throw an error, for example if the MEP is not an InOut. What is the incoming MEP ?
Cheers, Guillaume Nodet On 6/9/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
If an exchange is received by the routing slip, it should send it. On 6/9/06, Peter Klotz <[EMAIL PROTECTED] > wrote: > Hi Guillaume, > > hm, interesting, no the bes:usermgmt-filter is a transformer component > but the previous component that routes the request to the > bes:usermgmt-router > eip pattern is a custom eip pattern written by us that is based on the > content-based router. But that did work fine so far, and forwarded to > bes:dispatcher. So what I'm doing now is just introduce a > static-routing-slip > inbetween this custom content-based-router and the bes:dispatcher. > > The ME never arrives at usermgmt-filter, which I can see by means of my > debugger > waiting there :-) And in the debugger I also see that the custom > content-router > returns the right next target exchange (usermgmt-router). It also seems > from the > logfile that the exchange arrives at the usermgmt-router (the > static-routing-slip eip pattern) but that this component cannot forward > it to > the usermgmt-filter transformer component. > > Any more ideas? > > Guillaume Nodet wrote: > > AFAIK, the "No marching rule found for exchange" is sent by the > > ContentBasedRouter only. > > I bet the bes:usermgmt-filter is a content router, as it will be the > one > > sending this error. > >
