How many process in order to implement a multi-operations WSDL?

Question

Hello everyone,
I have designed a WSDL describing two operations, that I want to implement with BPEL.
I was wondering whether I needed to implement two BPEL files independently, one for each operation, or I was compelled to put the orchestration of both operations in a single BPEL file, with the help of a pick activity to separate the flows.
I tried both ways and only succeeded with the latter, but I am not convinced with the approach. The first option falls short when building the CASA. I get a "WARNING: 1 port with 2 providers", and effectively only one operation is exposed.
According to you, what is the way to go?
Thanks

Answer 1

Hi, Ricardo,
Why do you need to do this? What is the business requirement that demands this? It seems like a waste of time and effort, and you'll have to re-do it every time a row is INSERTed or DELETEd, or when any of the columns involved is UPDATEd.
Given that you really want to do it, here's one way:
MERGE INTO     table_x          dst
USING  (
           WITH    got_nums     AS
               SELECT  key1, key2, filename
            ,       ROW_NUMBER () OVER ( ORDER BY  key1 )
                                                   AS key_1_num
            ,       ROW_NUMBER () OVER ( ORDER BY  SUBSTR (filename, -8)
                                               ,         key2
                              )     AS filename_num
            FROM    table_x
        SELECT  k.key1
        ,        f.key2
        ,        f.filename
        FROM        got_nums     f
        JOIN        got_nums     k  ON  f.filename_num  = k.key_1_num
       )               src
ON     (src.filename     = dst.filename)          -- or any unique column(s), not including key1
WHEN MATCHED
THEN UPDATE  SET  dst.key1 = src.key1
;If you'd care to post CREATE TABLE and INSERT statements for the sample data, then I could test it.
As posted above, this assumes that filename is unique. If not, you'll have to change the join condition between src and dst to guarantee a unique match.
This does NOT assume that filename is always 19 characters; only that it is at least 8 characters, and that the last 8 characters determine the order.