Finding the Compromise – the Adapter Framework - Applied SOA Patterns on the Oracle Platform - page 391

'CustomerCode',
creditmonitoring_rec.customer_code);XXCU.XXCU_COMMON_UTIL_XML.print_xml_tag
(v_olob,'CountryRegistrationNumber',
creditmonitoring_rec.country_registration_number);XXCU.XXCU_COMMON_UTIL_XML.print_xml_tag
(v_olob, 'DUNSnumber',
creditmonitoring_rec.duns_number);XXCU.XXCU_COMMON_UTIL_XML.print_xml_tag
(v_olob,
'CustomerId',creditmonitoring_rec.customer_id);XXCU.XXCU_COMMON_UTIL_XML.print_xml_tag
(v_olob, 'CustomerId2',
creditmonitoring_rec.customer_id2);XXCU.XXCU_COMMON_UTIL_XML.print_xml_tag
(v_olob,
'Belop1',creditmonitoring_rec.belop1);XXCU.XXCU_COMMON_UTIL_XML.print_xml_tag
(v_olob, 'Belop2',
creditmonitoring_rec.belop2);XXCU.XXCU_COMMON_UTIL_XML.close_xml_tag
(v_olob, 'Company'); END LOOP;
(Please compare this approach with the pure XDB-based sample from the previous snip-
pet.) Close the tags, cursor, and temporary CLOB. Remember that CLOB is your output
parameter shown as follows:
CLOSE creditmonitoring_cur;
XXCU.XXCU_COMMON_UTIL_XML.close_xml_tag (v_olob,
'CreditMonitoring');op_olob :=
v_olob;XXCU.XXCU_COMMON_UTIL.closetmpclob (v_olob);
That's it, construction completed. Now you can construct any canonical message (cursors
are common and reusable, that was the purpose), or create individual messages for selec-
ted TPs quite easily, because the presented approach provides the highest granularity pos-
sible. Either way, transformation could be avoided, as we will have individual construct-
ors. Alternatively, to minimize the number of constructors, XDK transformation functions
could be used. Next, we will shortly explain the purpose of functions used in a message
construction as shown in the following table.
Tip
Generally, the functions are based on DBMS_LOB.WRITE not on
DBMS_OUTPUT.PUT_LINE .