Database Reference
In-Depth Information
business object, primary key data, and business domain. Of course, we have composite
context data recorded as an ADT array. What we want to know are two things—who is the
recipient (or in what compositions object, propagated as a message should participate),
and what would be the format of the message. We have already declared our main
goal—minimization of transformation and bridging; therefore, we will focus on recogni-
tion of the TP. Thus, we should link the object/object data with potential recipients, as we
explained when discussing Service Taxonomy in the previous chapter. Establishing the
rules, combined into rulesets, does it. Every object and list of associated events is linked
to one or more rulesets, where rules can be functions or XPath-based, as we discussed in
the previous chapter. When we have an object in native code for outbound processing, the
functional rules are more appropriate; please see the following code. Here we have the
simple function, returning location by ID. For Rule Engine simplification, we decided to
make all rule functions accepting only one parameter, which is initially our primary key:
FUNCTION get_AddressLocbyID(ip_addressid IN
xxcu_EHS_testaddress.adddress_id%type)
RETURN VARCHAR2
IS
CURSOR AddressbyID_cur (ip_addressid
xxcu_EHS_testaddress.adddress_id%type)
IS
SELECT xxcu_EHS_testaddress.adddress_id,
xxcu_EHS_testaddress.location,
xxcu_EHS_testaddress.description
FROM xxcu_EHS_testaddress
WHERE xxcu_EHS_testaddress.adddress_id =
ip_addressid;
AddressbyID_rec AddressbyID_cur%ROWTYPE;
v_address VARCHAR2 (400) := NULL;
BEGIN
OPEN AddressbyID_cur (ip_addressid);
FETCH AddressbyID_cur INTO AddressbyID_rec;
IF AddressbyID_cur%FOUND
THEN
IF AddressbyID_rec.location IS NULL
THEN
v_address := NULL;
ELSE
v_address := AddressbyID_rec.location;
Search WWH ::




Custom Search