Skip Headers

Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Linux x86 B25216-01 |
| Home | Contents

Previous | Next |

# 8 Oracle Business Rules

This chapter describes issues associated with Oracle Business Rules. It includes the following topics:

- Section 8.1, "Using RL Reserved Words in Java Package Names"

- Section 8.2, "Ancestor Methods are not Visible from Sub-Classes"

- Section 8.3, "New and Deleted Patterns are not Immediately Available"

- Section 8.4, "Changes to the Bind Variable Name are not Immediately Reflected"

## 8.1 Using RL Reserved Words in Java Package Names

Invalid RL Language is generated if an RL Language reserved word (for example, the word `rule` in `mypkg.rule.com`) is part of the Java package name. If an RL Language reserved word is used in a Java package name, an error message like the following appears:

    Oracle RL 1.0: syntax error PareseException: encountered 'rule' when expectingone of: <XML_IDENTIFIER> ...<IDENTIFIER> ... "*" at line 11 column 19 in main

There is no workaround for this issue; do not use RL Language reserved words in Java package names.

## 8.2 Ancestor Methods are not Visible from Sub-Classes

The properties of a superclass are visible in the appropriate choice lists, but the methods of the ancestor classes are not visible.

There is no workaround for this issue.

## 8.3 New and Deleted Patterns are not Immediately Available

When you use Rule Author to add a pattern to a rule, the list of actions does not immediately reflect the existence of the new pattern instance. Similarly, when you use Rule Author to delete a pattern from a rule, the list of actions does not immediately reflect this change.

To work around this issue, you can do either of the following:

1. Update the rule by clicking either OK or Apply, then re-select the rule from the navigation pane.

2. Create a new action.

## 8.4 Changes to the Bind Variable Name are not Immediately Reflected

If you change the bind variable name on the Pattern Definition page, this change is not immediately reflected on the parent page (the Rule Author Rule page). In order to see your changes, you must close the Pattern Definition page before continuing your work on the Rule Author Rule page.

There is no workaround for this issue.