Sencha Documentation

Super classes

The XML Reader is used by a Proxy to read a server response that is sent back in XML format. This usually happens as a result of loading a Store - for example we might create something like this:

Ext.regModel('User', {
    fields: ['id', 'name', 'email']
});

var store = new Ext.data.Store({
    model: 'User',
    proxy: {
        type: 'ajax',
        url : 'users.xml',
        reader: {
            type: 'xml',
            record: 'user'
        }
    }
});

The example above creates a 'User' model. Models are explained in the Model docs if you're not already familiar with them.

We created the simplest type of XML Reader possible by simply telling our Store's Proxy that we want a XML Reader. The Store automatically passes the configured model to the Store, so it is as if we passed this instead:

reader: {
    type : 'xml',
    model: 'User',
    record: 'user'
}

The reader we set up is ready to read data from our server - at the moment it will accept a response like this:

<?xml version="1.0" encoding="UTF-8"?>
<user>
    <id>1</id>
    <name>Ed Spencer</name>
    <email>[email protected]</email>
</user>
<user>
    <id>2</id>
    <name>Abe Elias</name>
    <email>[email protected]</email>
</user>

The XML Reader uses the configured record option to pull out the data for each record - in this case we set record to 'user', so each <user> above will be converted into a User model.

Reading other XML formats

If you already have your XML format defined and it doesn't look quite like what we have above, you can usually pass XmlReader a couple of configuration options to make it parse your format. For example, we can use the root configuration to parse data that comes back like this:

<?xml version="1.0" encoding="UTF-8"?>
<users>
    <user>
        <id>1</id>
        <name>Ed Spencer</name>
        <email>[email protected]</email>
    </user>
    <user>
        <id>2</id>
        <name>Abe Elias</name>
        <email>[email protected]</email>
    </user>
</users>

To parse this we just pass in a root configuration that matches the 'users' above:

reader: {
    type  : 'xml',
    root  : 'users',
    record: 'user'
}

Note that XmlReader doesn't care whether your root and record elements are nested deep inside a larger structure, so a response like this will still work:

<?xml version="1.0" encoding="UTF-8"?>
<deeply>
    <nested>
        <xml>
            <users>
                <user>
                    <id>1</id>
                    <name>Ed Spencer</name>
                    <email>[email protected]</email>
                </user>
                <user>
                    <id>2</id>
                    <name>Abe Elias</name>
                    <email>[email protected]</email>
                </user>
            </users>
        </xml>
    </nested>
</deeply>

Response metadata

The server can return additional data in its response, such as the total number of records and the success status of the response. These are typically included in the XML response like this:

<?xml version="1.0" encoding="UTF-8"?>
<total>100</total>
<success>true</success>
<users>
    <user>
        <id>1</id>
        <name>Ed Spencer</name>
        <email>[email protected]</email>
    </user>
    <user>
        <id>2</id>
        <name>Abe Elias</name>
        <email>[email protected]</email>
    </user>
</users>

If these properties are present in the XML response they can be parsed out by the XmlReader and used by the Store that loaded it. We can set up the names of these properties by specifying a final pair of configuration options:

reader: {
    type: 'xml',
    root: 'users',
    totalProperty  : 'total',
    successProperty: 'success'
}

These final options are not necessary to make the Reader work, but can be useful when the server needs to report an error or if it needs to indicate that there is a lot of data available of which only a subset is currently being returned.

Response format

Note: in order for the browser to parse a returned XML document, the Content-Type header in the HTTP response must be set to "text/xml" or "application/xml". This is very important - the XmlReader will not work correctly otherwise.

Config Options

 
id : String
DEPRECATED - this will be removed in Ext JS 5.0. Please use idProperty instead
DEPRECATED - this will be removed in Ext JS 5.0. Please use idProperty instead
 
idPath : String
DEPRECATED - this will be removed in Ext JS 5.0. Please use idProperty instead
DEPRECATED - this will be removed in Ext JS 5.0. Please use idProperty instead
 
idProperty : String
Name of the property within a row object that contains a record identifier value. Defaults to id
Name of the property within a row object that contains a record identifier value. Defaults to id
 
True to automatically parse models nested within other models in a response object. See the Ext.data.Reader intro doc...
True to automatically parse models nested within other models in a response object. See the Ext.data.Reader intro docs for full explanation. Defaults to true.
 
The name of the property which contains a response message. This property is optional.
The name of the property which contains a response message. This property is optional.
 
record : String
The DomQuery path to the repeated element which contains record information. This is an alias for the root config opt...
The DomQuery path to the repeated element which contains record information. This is an alias for the root config option.
 
root : String
Required. The name of the property which contains the Array of row objects. Defaults to undefined. An exception wil...
Required. The name of the property which contains the Array of row objects. Defaults to undefined. An exception will be thrown if the root property is undefined. The data packet value for this property should be an empty array to clear the data or show no data.
 
success : String
DEPRECATED - this will be removed in Ext JS 5.0. Please use successProperty instead
DEPRECATED - this will be removed in Ext JS 5.0. Please use successProperty instead
 
Name of the property from which to retrieve the success attribute. Defaults to success. See Ext.data.DataProxy.excep...
Name of the property from which to retrieve the success attribute. Defaults to success. See Ext.data.DataProxy.exception for additional information.
 
totalProperty : String
Name of the property from which to retrieve the total number of records in the dataset. This is only needed if the wh...
Name of the property from which to retrieve the total number of records in the dataset. This is only needed if the whole dataset is not passed in one go, but is being paged from the remote server. Defaults to total.

Properties

 
rawData : Mixed
The raw data object that was last passed to readRecords. Stored for further processing if needed
The raw data object that was last passed to readRecords. Stored for further processing if needed
 
xmlData : Object
DEPRECATED - will be removed in Ext JS 5.0. This is just a copy of this.rawData - use that instead
DEPRECATED - will be removed in Ext JS 5.0. This is just a copy of this.rawData - use that instead

Methods

 
getData( Object data ) : Object
Normalizes the data object
Normalizes the data object

Parameters

  • data : Object
    The raw data object

Returns

  • Object   Returns the documentElement property of the data object if present, or the same object if not
 
getResponseData( Object response ) : Object
Takes a raw response object (as passed to this.read) and returns the useful data segment of it. This must be implemen...
Takes a raw response object (as passed to this.read) and returns the useful data segment of it. This must be implemented by each subclass

Parameters

  • response : Object
    The responce object

Returns

  • Object   The useful data from the response
 
read( Object response ) : Ext.data.ResultSet
Reads the given response object. This method normalizes the different types of response object that may be passed to ...
Reads the given response object. This method normalizes the different types of response object that may be passed to it, before handing off the reading of records to the readRecords function.

Parameters

  • response : Object
    The response object. This may be either an XMLHttpRequest object or a plain JS object

Returns

  • Ext.data.ResultSet   The parsed ResultSet object
 
readRecords( Object doc ) : Ext.data.ResultSet
Parses an XML document and returns a ResultSet containing the model instances
Parses an XML document and returns a ResultSet containing the model instances

Parameters

  • doc : Object
    Parsed XML document

Returns

  • Ext.data.ResultSet   The parsed result set