More about HTML Fragment rules

Use HTML fragment rules to define universally available HTML parts, such as style sheets and scripts, including JavaScript files. During stream processing, a JavaServer Pages (JSP) tag can insert this text into other HTML rule instances.

Comparing HTML fragments with HTML rules

You can create a "universal" part in an HTML rule by using the ultimate base class ( @baseclass ) as the Applies To part of the key.

If you use an HTML fragment instead, then at runtime the system avoids the overhead of the class inheritance algorithm, improving runtime performance.

Comparing HTML fragments with static Web server files

If the HTML (or scripts or style sheets) text does not contain JavaServer Pages (JSP) tags, you can place the HTML in a text file rule rather than in a fragment rule. The system exports a text file rule to an appropriate directory the first time that the file is needed. In contrast to fragment rules, text file rules are not processed again, so using this approach improves performance.

You can incorporate static elements into your HTML forms and displays using normal HTML means, such as the following in the <HEAD> section:

<SCRIPT SRC="filename.js" TYPE="text/JavaScript>


<LINK HREF="ruleprostylesheet.css" REL="STYLESHEET" TYPE="text/css">

You can view the generated Java code of a rule by clicking Actions > View Java. You can use this code to debug your application or to examine how rules are implemented.

Parent class

Through directed inheritance, the immediate parent class of the Rule-HTML-Fragment class is the Rule-Stream class.


If your application rulesets contain HTML-Fragment rules, run the Rule Security Analyzer before locking a ruleset version, to look for possible security issues.