Listing Styles General-Purpose Listing Styles Used by a Predefined Theme General-Purpose

MapViewer XML Requests: Administrative and Other 7-9 The name attribute identifies each theme. For example: ?xml version=1.0 ? non_map_response predefined_theme_list succeed=true predefined_theme name=THEME_DEMO_CITIES predefined_theme name=THEME_DEMO_BIGCITIES predefined_theme name=THEME_DEMO_COUNTIES predefined_theme name=THEME_DEMO_COUNTY_POPDENSITY predefined_theme name=THEME_DEMO_HIGHWAYS predefined_theme name=THEME_DEMO_STATES predefined_theme name=THEME_DEMO_STATES_LINE predefined_theme_list non_map_response Note that the order of names in the returned list is unpredictable.

7.4 Listing Styles General-Purpose

The list_styles element lists styles defined for a specified data source. It has the following definition: ELEMENT non_map_request list_styles ELEMENT list_styles EMPTY ATTLIST list_styles data_source CDATA REQUIRED style_type COLOR|LINE|MARKER|AREA|TEXT|ADVANCED IMPLIED If you specify a value for style_type, only styles of that type are listed. The possible types of styles are COLOR, LINE, MARKER, AREA, TEXT, and ADVANCED. If you do not specify style_type, all styles of all types are listed. The following example lists only styles of type COLOR: ?xml version=1.0 standalone=yes? non_map_request list_styles data_source=mvdemo style_type=COLOR non_map_request The DTD for the response to a list_styles request has the following format: ELEMENT non_map_response style_list ELEMENT style_list style ATTLIST style_list succeed true | false REQUIRED ELEMENT style EMPTY ATTLIST style name CDATA REQUIRED The following example shows the response to a request for styles of type COLOR: ?xml version=1.0 ? non_map_response style_list succeed=true style name=SCOTT:C.BLACK style name=SCOTT:C.BLACK GRAY style name=SCOTT:C.BLUE 7-10 Oracle Fusion Middleware Users Guide for Oracle MapViewer style name=SCOTT:C.CRM_ADMIN_AREAS style name=SCOTT:C.CRM_AIRPORTS style_list non_map_response Each style name in the response has the form OWNER:NAME for example, SCOTT:C.BLACK, where OWNER is the schema user that owns the style.

7.5 Listing Styles Used by a Predefined Theme General-Purpose

The list_theme_styles element lists all the rendering styles that are referenced in a predefined theme. This is particularly useful if you want to build a legend for a theme yourself, where you need to know which styles are actually being used in that theme. This element has the following definition: ELEMENT non_map_request list_theme_styles ELEMENT list_theme_styles EMPTY ATTLIST list_styles data_source CDATA REQUIRED theme CDATA REQUIRED The following example requests the styles used by the THEME_DEMO_STATES predefined theme: non_map_request list_theme_styles data_source=mvdemo theme=THEME_DEMO_STATES non_map_request The following example shows the response to the preceding request: non_map_response theme_style name=C.US MAP YELLOW type=COLOR render=true label=false highlight=false description=Primary color for US maps. theme_style name=T.STATE NAME type=TEXT render=false label=true highlight=false description=name for states non_map_response The DTD for the response to a list_theme_styles request has the following format: ELEMENT non_map_response theme_style ELEMENT theme_style EMPTY ATTLIST theme_style name CDATA REQUIRED type CDATA COLOR|LINE|MARKER|AREA|TEXT|ADVANCED REQUIRED render CDATA true|false REQUIRED label CDATA true|false REQUIRED highlight CDATA true|false REQUIRED description CDATA IMPLIED In the preceding DTD: ■ The name attribute identifies the name of the style. ■ The type attribute identifies the MapViewer style type. ■ The render attribute indicates whether or not the style is used as a rendering style by the theme. ■ The label attribute indicates whether or not the style is used as a labeling style. MapViewer XML Requests: Administrative and Other 7-11 ■ The highlight attribute indicates whether or not the style is used as only a highlight style. ■ The description attribute identifies the description as specified in the style definition.

7.6 Managing In-Memory Caches