You can use JDeveloper to create BI Beans JSP tags. A JDeveloper wizard prompts you for information related to the tag that you want to create and inserts the coded tag in the JSP page. You can edit BI Beans JSP tags in JDeveloper.
The following concepts are presented to aid your understanding of BI Beans JSP tags and to assist in avoiding errors if you edit the JSP tags:
Identification of the BI Beans JSP tag library
BIThinSession tag must appear first
Programming model: Define and render
Use InsertHiddenFields tag in each form
Thread-safe processing for BI Beans JSP tags
The following information identifies the tag library for BI Beans JSP tags:
Tag library URI: /webapp/BITags.tld
Tag library prefix: orabi
The first tag that you create must be a BIThinSession tag. BIThinSession must occur before the first Render tag in the JSP.
JDeveloper inserts the BIThinSession tag before the default <FORM> element that it also inserts in the JSP.
The thin beans that are instantiated by the BI Beans JSP tags are interdependent and need to send and process events. To facilitate this processing, BI Beans JSP tags observe the following programming requirements for each bean that is to appear in a page:
Insert a content tag, within the BIThinSession tag, to define the bean that is to appear in the JSP.
Insert a Render tag for each bean that is to appear in the JSP.
JDeveloper observes these two requirements automatically when you finish a wizard for a BI Beans JSP tag. That is, JDeveloper inserts a content tag within the BIThinSession tag and a Render tag at the location of the cursor in the <FORM> element of the page.
Note: Do not insert any other code inside the BIThinSession tag and do not write code that refers to a bean until after the end of the BIThinSession tag.
In each form, the InsertHiddenFields tag must appear as the last tag before the </FORM> element. This tag inserts hidden fields that are related to state and event handling.
To provide thread-safe processing for the BI Beans JSP tags, JDeveloper inserts automatically a synchronized scriptlet to create a block of code that is synchronized on a session object. The BI Beans JSP tags must be contained within this block of code to prevent unexpected results when multiple requests are processed.