Pattern matching

All requests are compared with installed REQUESTMODEL values for CORBASERVER and TYPE. A TYPE value of CORBA indicates a request for a stateless CORBA object; a TYPE value of EJB indicates a request for an enterprise bean, and a TYPE value of GENERIC can indicate either type of request. Further matching is then performed, based on the TYPE value:

Stateless CORBA objects
For stateless CORBA objects, (TYPE=CORBA, or GENERIC), the matching process compares the MODULE name, INTERFACE and OPERATION fields contained within the IIOP message, against the patterns defined in each installed REQUESTMODEL, until the closest match is found. INTERFACE, MODULE, and OPERATION can be defined as generic patterns. The rules for pattern matching are summarized as follows:
  • Double colons are used as component separators. Each component must be between 1 and 16 characters long
  • Generic patterns can consist of zero or more characters followed by *.

If several different generic patterns match a given string, the longest generic pattern results in the most specific match.

Enterprise beans
For enterprise beans, the matching process compares the BEANNAME, OPERATION, and INTFACETYPE fields within the IIOP message, against those defined in each installed REQUESTMODEL.