Hi,
I am looking at the bpe component.
I would like a routing component to do all the routing of messages
coming out of the BPEL engine, instead of doing it in the bpel. i.e.
letting the NMR take care of it, using some content based routing
component.
So, I suppose I could have all my <bpel:invokes ..> always sending to
the router ... but, well, if they all go via the router, is it possible
to simplify the <bpel:invokes ..>
If set the destinationService of the BPEL component to my router. The
BPEL engine then doesn't do routing, but does control the ordering, etc
of messages leaving it - it just sends out and receives XML.
The thing is then - I think - I don't need (and don't want) the
operation and porttype attributes on the <bpel:invoke ... >, but I was
trying that, and BPE doesn't allow these to be omitted.
Does that all make sense / is possible ?
thanks !
Roger
