This section defines:

• Default Domino tag attributes
• Supplying attribute values
• Standard JSP variables
• Search order for default values

The following table displays the variables you can set as defaults for the corresponding attributes of a Domino JSP tag. These variables create either of the following attributes:

• lotus.domino.default.Variable Name
• lotus.domino.preset.Variable Name

Attribute	Variable Name	Description	Contained by
bundle	msgbundle	Name of the message bundle to use to look up internationalized messages. Default is: messages
host	host	Name of the Common Object Request Broker Architecture (CORBA) server that the tags will communicate with instead of using the local Notes Object Interface (NOI) calls. If no session tag is used, all the tags will check for the existence of this attribute to initialize the NOI session. All "Local" databases are considered local to the CORBA server.	db, form, ftsearch, session, view
dbname	dbname	Name of the database being accessed.	db, form, ftsearch, view
dbserver	dbserver	Name of a remote Domino server that hosts the database being accessed. This attribute is not often used. It should be specified if the data content for an application is stored in a different database from the database storing the design data for the application. Default is: Local	db, form, ftsearch, view
locale	locale	Name of the locale to use to look up internationalized messages or to perform output formatting. Use this format: <languageCode>_<countryCode> By default, the locale is derived by the container from the browser's Acceptlang string. See Locale codes for language and country code information.
onfailure	onfailure	Indicates how a failure should be handled. Must be either: inline or exception.	All tags
password	password	Password associated with the specified user ID. Note If you supply the password this way - using a default page parameter, it will be exposed in the URL string. You can prevent this by using container-managed access.	db , form, ftsearch, session, view
responseto	responseto	Domino Unique ID of the parent document that a response document responds to.	form
timezone	timezone	Time zone to use to format and parse dates. Defaults to the time zone of the server (not the browser).	All tags
unid	unid	Domino Unique ID for the context document.	form
user	user	User ID used to log into the session. Default is Anonymous.	db , form, ftsearch, session tag, view
viewname	viewname	Name of the view to display or to use as the view context for the form or query.	form, view

The JSP tags always look for these attribute values to be supplied as:

1. an explicitly supplied attribute:

<item name="datepicker" format="<LI> DATE=FULL" locale="en_us" onfailure="inline" />

• the context-param tag in the web.xml file for the application with either a preset or default variable name:

<context-param>
<param-name>lotus.domino.default.onfailure</param-name>
<param-value>inline</param-value>
</context-param>
• the preset or default tags in the JSP page:

<domino:default scope="page" onfailure="inline"/>

Both methods set the default onfailure attribute for the page to inline, which instructs the page to display any errors thrown by a tag directly on the page in bold text at the tag location when the page executes.

• pageContext.setAttribute(name, value, scope), where the scope parameter is one of the following:

PageContext.APPLICATION_SCOPE
PageContext.SESSION_SCOPE
PageContext.REQUEST_SCOPE
PageContext.PAGE_SCOPE

For example:

pageContext.setAttribute("lotus.domino.default.onfailure", "inline", PageContext.PAGE_SCOPE)

• the preset or default tag in the JSP page:

<domino:default scope="page" onfailure="inline"/>

http://myserver/myformpage.jsp?dbname=test.nsf&unid=ABE518A8255B371685256A47006AF2B7&onfailure=inline

For example, the default for the pages attribute of the pagebar tag is 10. You can find the default values for the tag attributes in the tag descriptions provided in this document.

Standard JSP variables

The following table contains the standard JSP variables that you can use in your pages:

The following table demonstrates the hierarchy the JSP tags use to search the environment for the values of the default tag attributes if one of them is not supplied:

Scope	Retrieval Method	Variable Name(<varname>)
Tag	attribute value
ServletContext	ServletContext.getInitParameter()	lotus.domino.preset.<varname>
APPLICATION_SCOPE	PageContext.getAttribute()	lotus.domino.preset.<varname>
SESSION_SCOPE	PageContext.getAttribute()	lotus.domino.preset.<varname>
REQUEST_SCOPE	PageContext.getAttribute()	lotus.domino.preset.<varname>
PAGE_SCOPE	PageContext.getAttribute()	lotus.domino.preset.<varname>
Query string	HTTPServletRequest.getParameter()	<varname>
PAGE_SCOPE	PageContext.getAttribute()	lotus.domino.default.<varname>
REQUEST_SCOPE	PageContext.getAttribute()	lotus.domino.default.<varname>
SESSION_SCOPE	PageContext.getAttribute()	lotus.domino.default.<varname>
APPLICATION_SCOPE	PageContext.getAttribute()	lotus.domino.default.<varname>
ServletContext	ServletContext.getInitParameter()	lotus.domino.default.<varname>

See Also

The Domtags tag library

Glossary