GXE Structure
Pages 202
- Home
- 2009 Esri Federal UC
- 2009 Esri International UC
- 2010 Esri Federal UC
- 2010 Esri International UC
- 2011 Esri Federal UC
- 2012 Esri Federal UC
- 2013 Esri Federal GIS Conference
- 2013 Esri International User Conference
- 2015 SDI Special Interest Group
- Add a Custom Profile
- Add an OpenSearch endpoint for Federated Search
- Add Another Tab to the Geoportal Interface
- Add Custom Link to a Search Result
- Add Custom Search Criteria
- Add the Geoportal Search to a List of Search Providers
- Add v1.1.1 FGDC editor to a previous Geoportal release
- AGP TO AGP Harvesting with the Geoportal
- AGS TO AGP Harvesting with the Geoportal
- All gpt.xml file settings
- An Introduction to vi
- Apache Tomcat geoportal logging
- Being a Good Robot
- Best Practice for Edits to JSP files
- Biological or Remote Sensing FGDC xsds
- Browse Tree
- Cart Processor
- Catalog Service
- Clear the Tomcat Work Folder
- Collections
- Common problems and solutions
- Communities and live examples
- Components
- Configure a Directory Server for the Geoportal
- Configure geoportal User and Schema in the PostgreSQL Database
- Configure Previewable Filetypes
- Configure Searching of YouTube
- Configure the gpt.xml File
- Configure Widgets
- Connecting to a User Directory
- Create a user account
- Create Relationships between Resources
- Customizations
- Customize DCAT output
- Customize Metadata Validation
- Database problems
- Database Tables
- DataDownload Tab
- Deploy and Configure the Geoportal Web Application in Tomcat
- Deploy and Configure the Servlet Web Application
- Deploy the Geoportal Web Application
- Details of Lucene Indexing in the Geoportal
- Development topics
- Discovering Resources
- Eclipse Project from Compiled WAR
- Eclipse Project from Source Code
- Enable Search Using an Ontology Service
- Error Messages in the Geoportal Web Application
- Esri Geoportal Server LiveDVD
- Extending the Web Harvester
- Federated Search in Portal for ArcGIS
- Feedback
- FGDC Biological Profile and Remote Sensing Extension
- FGDC Service Checker Integration
- Geoportal Clients for ArcGIS
- Geoportal CSW Clients
- Geoportal Facets using Apache Solr
- Geoportal genie
- Geoportal Project from Compiled WAR
- Geoportal Publish Client
- Geoportal Server 1.2.5 What's New
- Geoportal Server 1.2.6 What's New
- Geoportal Server 1.2.7 What's New
- Geoportal server as a broker
- Geoportal Server Downloads
- Geoportal Server v 1.0 What's New
- Geoportal Server v 1.1 What's New
- Geoportal Server v 1.1.1 What's New
- Geoportal Server v 1.2 What's New
- Geoportal Server v 1.2.2 What's New
- Geoportal Server v 1.2.4 What's New
- Geoportal SPARQL Sample
- Geoportal User Interface Components
- Geoportal Web Application File Organization
- Geoportal XML Editor
- Get Assistance with an Implementation
- GXE Concepts
- GXE Crash Course
- GXE Structure
- GXE Workflow
- High Availability and Large Number of Records
- How to Browse for Resources
- How to Create and Manage My Profile
- How to find all documents of a particular metadata standard
- How to Leave a Resource Review
- How to Login and Manage my Password
- How to Manage and Edit Resources
- How to Publish Resources
- How to Restrict Access to Resources
- How to Search for Resources
- How to Search with an Ontology Service
- How to Set Up an Esri Geoportal Server on Linux
- How to Use Search Page Results
- How to Use the Data Download Feature
- How to View Resource Relationships
- IDE Topics
- Identity Components LDAP and Single Sign On
- Index All Metadata Content
- Indexing and Searching the Time Period of the Content
- Install Apache Tomcat 6
- Install Desktop Tools
- Install Esri Geoportal Server
- Install PostgreSQL 9.1.2
- Install the JDBC .jar Files
- Installation
- Installation Version 1.0
- Installation Version 1.1
- Installation Version 1.2
- Installation Version 1.2.2
- Installation Version 1.2.4
- Installation Version 1.2.5
- Installation Version 1.2.6
- Installation Version 1.2.7
- Installation Version 1.2.8
- Integrate with a Content Management System
- Integrate with the con terra Security Solution
- Localization
- Log In to the Geoportal
- Logging
- Look and Feel of the User Interface
- Main Page
- Map LDAP Attributes on the Registration Page
- Map Viewer
- Online form editing for all publication methods
- Open source acknowledgements
- Oracle WebLogic geoportal logging
- Orientation to the Create Metadata Page
- Perform Preinstallation Computer Setup
- Portal for ArcGIS Integration
- Post Deployment Actions
- Preinstallation
- Preinstallation 0.9
- Preinstallation 1.0 and 1.1.x
- Preinstallation 1.2
- Preinstallation 1.2.2
- Preinstallation 1.2.4
- Preinstallation 1.2.5
- Preinstallation 1.2.6
- Preinstallation 1.2.7
- Preinstallation 1.2.8
- Preview Function
- Publication Components
- Ratings and Comments for Search Results
- Register ArcGIS for Server with the Geoportal
- Release notes
- REST API Syntax
- Sample FGDC metadata.xml
- Scheduled tasks
- Search Components
- Search Map
- Search Widget for Flex
- Search Widget for HTML
- Search Widget for Silverlight
- Security Concepts
- Set Up Systemwide Environment Variables
- Set up the Geoportal Database
- Share Link
- Single Sign On
- Smoketest the Geoportal
- Standards Support
- Supported CSW Profiles for Synchronization
- Theme Library
- Troubleshooting
- Troubleshooting Tips
- Two geoportals on the same server
- Upgrade 1.x to 1.2 database
- Upgrading file system approach
- Upgrading Read This Overview
- Upgrading SVN approach
- Url filter customization
- Use an XSLT to Render the Details Page
- Use Ant to build Geoportal
- User Functions and Roles
- User Management Interface
- Using a geoportal
- Using Lucene Search Text Queries
- Version 0.9
- Version 1.0
- Version 1.1
- Version 1.1.1
- Version 1.2
- Version 1.2.2
- Version 1.2.4
- Version 1.2.5
- Version 1.2.6
- Version 1.2.7
- Version 1.2.8
- What is a geoportal and the geoportal server
- What is the esri geoportal server
- What's New
- wiki template
- WMC Client
- Show 187 more pages…
Clone this wiki locally
GXE is intended to support metadata profiles or additional metadata schemas. This section describes how to configure GXE for this as well as how to alter the behavior of the editor for existing metadata schemas. For general introduction and additional topics, see Geoportal XML Editor. After reading this topic, you can work through the GXE Crash Course to become familiar with customizing the GXE Editor.
Core Geoportal XML Editor Definition Structure
The files that define the core structure for the editor are located within the [webapp]/WEB-INF/classes/gpt/gxe directory. These files provide a foundation for reuse when defining the content of an editor. Although it is not mandatory to extend an editor from these files, the editors that ship with the Geoportal Server all extend from this core.
-
[webapp]/WEB-INF/classes/gpt/gxe/editor.xmlThis is the base editor from which all other editors extend.
The ui Subdirectory
The directory at [webapp]/WEB-INF/classes/gpt/gxe/core/ui contains a collection of reusable files
associated with the binding of editor components to the user interface. Below is a description of files found in the ui directory.
-
[webapp]/WEB-INF/classes/gpt/gxe/core/uiA collection of reusable files associated with the binding of editor components to the user interface. -
[webapp]/WEB-INF/classes/gpt/gxe/core/ui/InputText.xmlseful for binding an input text box to the value of a target XML node (element text or attribute). The default definition will render an HTML<input>tag of type text with a size of 60 and max length of 2048. A JavaScript object of typegxe.control.InputTextwill be instantiated to process the component.
<h:input xmlns:g="http://www.esri.com/geoportal/gxe" xmlns:h="http://www.esri.com/geoportal/gxe/html" h:tag="input" h:type="text" h:size="60" h:maxlength="2048" g:jsClass="gxe.control.InputText"/>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/ui/InputTextArea.xmlUseful for binding an input text area box to the value of a target XML node (element text). The default definition will render an HTML<textarea>tag of type text with 46 columns and 3 rows. A JavaScript object of typegxe.control.InputTextAreawill be instantiated to process the component.
<h:textarea xmlns:g="http://www.esri.com/geoportal/gxe" xmlns:h="http://www.esri.com/geoportal/gxe/html" h:tag="textarea" h:cols="46" h:rows="3" g:jsClass="gxe.control.InputTextArea"/>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/ui/InputSelectOne.xmlUseful for binding a select dropdown to the value of a target XML node (element text or attribute). The default definition will render an HTML<select>tag. A JavaScript object of typegxe.control.InputSelectOnewill be instantiated to process the component. The selectable options are provided by the definition component extending this file.
<h:select xmlns:g="http://www.esri.com/geoportal/gxe" xmlns:h="http://www.esri.com/geoportal/gxe/html" h:tag="select" g:jsClass="gxe.control.InputSelectOne"> <g:options g:overridable="true"/> </h:select>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/ui/InputSelectMany.xmlUseful for binding a multiple checkbox control to the values associated with a repeatable XML target node (element text). The default definition will render an HTML <ul> tag with a CSS class namedgxeSelectMany. A JavaScript object of typegxe.control.InputSelectManywill be instantiated to process the component. The selectable options are provided by the definition component extending this file, and will be rendered as checkboxes within HTML<li>tag.
<h:ul xmlns:g="http://www.esri.com/geoportal/gxe" xmlns:h="http://www.esri.com/geoportal/gxe/html" h:tag="ul" h:class="gxeSelectMany" g:jsClass="gxe.control.InputSelectMany"> <g:options g:overridable="true"/> </h:ul>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/ui/InputDelimitedTextArea.xmlUseful for binding an input text area box (comma delimited by default) to the values associated with a repeatable XML target node (element text). The default definition will render an HTML<textarea>tag of type text with 60 columns and 10 rows. A JavaScript object of typegxe.control.InputDelimitedTextAreawill be instantiated to process the component.
The xml Subdirectory
The directory at [webapp]/WEB-INF/classes/gpt/gxe/core/xml contains a collection of reusable files associated with the binding of editor components to the targeted XML mapping. Below is a description of files found in the xml directory.
-
[webapp]/WEB-INF/classes/gpt/gxe/core/xml/Element.xmlUseful for binding a user interface component to a complex target XML element type (i.e. an element that has an attribute or children). This definition component extends from$base/core/ui/Section.xml(i.e., inherits structure and behavior). The qualified name for the component will be overridden asg:element. The JavaScript object (g:jsClass) instantiated to process the component will be overridden asgxe.control.Element.
<g:element xmlns:g="http://www.esri.com/geoportal/gxe" xmlns:h="http://www.esri.com/geoportal/gxe/html" g:jsClass="gxe.control.Element" g:extends="$base/core/ui/Section.xml"/>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/xml/ElementTextOnly.xmlUseful for binding a user interface component to a simple target XML element type (i.e., an element that has text content but no attribute or children). This definition component adds an input text box to the body of the underlying section. The input component is flagged as overridable and can be replaced if required by a component that extends this component.
<g:element xmlns:g="http://www.esri.com/geoportal/gxe"
xmlns:h="http://www.esri.com/geoportal/gxe/html"
g:extends="$base/core/xml/Element.xml">
<g:body>
<g:input g:overridable="true" g:extends="$base/core/ui/InputText.xml"/>
</g:body>
</g:element>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/xml/Attribute.xmlUseful for binding a user interface component to a target XML attribute. This definition component adds an input text box to the body of the underlying section. The input component is flagged as overridable and can be replaced if required by a component that extends this component.
<g:attribute xmlns:g="http://www.esri.com/geoportal/gxe"
xmlns:h="http://www.esri.com/geoportal/gxe/html"
g:jsClass="gxe.control.Attribute"
g:extends="$base/core/ui/Section.xml">
<g:body>
<g:input g:overridable="true" g:extends="$base/core/ui/InputText.xml"/>
</g:body>
</g:attribute>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/xml/ElementChoice.xmlUseful for binding an exclusive user interface choice component to a list of target XML element. A section will be added to the user interface (HTML<div>tag with a CSS class namedgxeTabs, processed by a JavaScript object of typegxe.control.ElementChoice). A header will be added to the section (HTML<div>tag with a CSS class named gxeTabsHeader). An array of tabs will be added to the header (HTML<ul>tag with a CSS class namedgxeTabArray, processed by a JavaScript object of typegxe.control.TabArray). A body will be added to the section (HTML<div>tag with a CSS class namedgxeTabsBody, processed by a JavaScript object of typegxe.control.ElementChoiceBody). A radio button will be generated for each child declared within the body. Only one of these children will be selected at any given time, and only that element will be serialized within the resultant XML document.
<g:elementChoice xmlns:g="http://www.esri.com/geoportal/gxe"
xmlns:h="http://www.esri.com/geoportal/gxe/html"
h:tag="div" h:class="gxeTabs"
g:label="$i18n.catalog.gxe.general.choose"
g:labelNone="$i18n.catalog.gxe.general.choose.none"
g:jsClass="gxe.control.ElementChoice">
<g:header g:extensible="true" h:tag="div" h:class="gxeTabsHeader">
<g:label g:extensible="true" h:tag="label"
h:class="gxeElementChoiceCaption"/>
<g:tabArray h:tag="ul" h:class="gxeTabArray"
g:jsClass="gxe.control.TabArray"/>
</g:header>
<g:body g:extensible="true" h:tag="div" h:class="gxeTabsBody"
g:jsClass="gxe.control.ElementChoiceBody"/>
</g:elementchoice>
-
[webapp]/WEB-INF/classes/gpt/gxe/core/xml/TextNode.xmlUseful for binding a user interface component to text content of a complex target XML type (i.e., an element that has text content but no attribute or children). This definition component adds an input text box to the body of the underlying section. The input component is flagged as overridable and can be replaced if required by a component that extends this component.
<g:textNode xmlns:g="http://www.esri.com/geoportal/gxe"
xmlns:h="http://www.esri.com/geoportal/gxe/html"
g:extends="$base/core/ui/Section.xml">
<g:body>
<g:input g:overridable="true" g:extends="$base/core/ui/InputText.xml"/>
</g:body>
</g:textnode>
Back to Geoportal XML Editor