Hi,
unfortunately it won't be possible for me to make the routing decision
with filters as you described. I do not want to use the destination
service as the decision key - what I would like to do is introduce a new
soap header containing a link to an external process describing the
routing. Each intermediary then takes this information and asks the
process (BPEL) what to do next. So it is kind of like an orchestration
service for additional services like logging etc... I described this in
a little more detail in my answer to Thomas Kelly`s mail in this thread.
Paul Fremantle wrote:
> You can actually do something like this with Axis2, but the Axis2
> design is actually there to figure out the order of handlers
> based on the "standard" pattern, so you would have to bypass that and
> use the services.xml to completely specify the handler order.
Could you describe that in a little more detail? I do not have a clue as
to where I can change the handler sequence at runtime from within a
handler. I don't even know if doing so would also affect other messages'
processing - which of course wouldn't be wanted at all.
Fred.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
