java.lang.ObjectClass supporting access to configuration settings.javax.servlet.jsp.jstl.core.Config
| Field Summary | ||
|---|---|---|
| public static final String | FMT_LOCALE | Name of configuration setting for application- (as opposed to browser-) based preferred locale |
| public static final String | FMT_FALLBACK_LOCALE | Name of configuration setting for fallback locale |
| public static final String | FMT_LOCALIZATION_CONTEXT | Name of configuration setting for i18n localization context |
| public static final String | FMT_TIME_ZONE | Name of localization setting for time zone |
| public static final String | SQL_DATA_SOURCE | Name of configuration setting for SQL data source |
| public static final String | SQL_MAX_ROWS | Name of configuration setting for maximum number of rows to be included in SQL query result |
| Method from javax.servlet.jsp.jstl.core.Config Summary: |
|---|
| find, get, get, get, get, remove, remove, remove, remove, set, set, set, set |
| Methods from java.lang.Object: |
|---|
| clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from javax.servlet.jsp.jstl.core.Config Detail: |
|---|
For each of the JSP scopes (page, request, session, application), get the value of the configuration variable identified by name using method get(). Return as soon as a non-null value is found. If no value is found, get the value of the context initialization parameter identified by name. |
The lookup of configuration variables is performed as if each scope had its own name space, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
The lookup of configuration variables is performed as if each scope had its own name space, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
The lookup of configuration variables is performed as if each scope had its own name space, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
The lookup of configuration variables is performed as if each scope had its own name space, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
Removing a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not impact one stored in a different scope. |
Removing a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not impact one stored in a different scope. |
Removing a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not impact one stored in a different scope. |
Removing a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not impact one stored in a different scope. |
Setting the value of a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
Setting the value of a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
Setting the value of a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |
Setting the value of a configuration variable is performed as if each scope had its own namespace, that is, the same configuration variable name in one scope does not replace one stored in a different scope. |