Skip to content

Most visited

Recently visited

added in API level 8


public interface LSResourceResolver

LSResourceResolver provides a way for applications to redirect references to external resources.

Applications needing to implement custom handling for external resources can implement this interface and register their implementation by setting the "resource-resolver" parameter of DOMConfiguration objects attached to LSParser and LSSerializer. It can also be register on DOMConfiguration objects attached to Document if the "LS" feature is supported.

The LSParser will then allow the application to intercept any external entities, including the external DTD subset and external parameter entities, before including them. The top-level document entity is never passed to the resolveResource method.

Many DOM applications will not need to implement this interface, but it will be especially useful for applications that build XML documents from databases or other specialized input sources, or for applications that use URNs.

Note: LSResourceResolver is based on the SAX2 [SAX] EntityResolver interface.

See also the Document Object Model (DOM) Level 3 Load and Save Specification.


Public methods

abstract LSInput resolveResource(String type, String namespaceURI, String publicId, String systemId, String baseURI)

Allow the application to resolve external resources.

Public methods


added in API level 8
LSInput resolveResource (String type, 
                String namespaceURI, 
                String publicId, 
                String systemId, 
                String baseURI)

Allow the application to resolve external resources.
The LSParser will call this method before opening any external resource, including the external DTD subset, external entities referenced within the DTD, and external entities referenced within the document element (however, the top-level document entity is not passed to this method). The application may then request that the LSParser resolve the external resource itself, that it use an alternative URI, or that it use an entirely different input source.
Application writers can use this method to redirect external system identifiers to secure and/or local URI, to look up public identifiers in a catalogue, or to read an entity from a database or other input source (including, for example, a dialog box).

type String: The type of the resource being resolved. For XML [XML 1.0] resources (i.e. entities), applications must use the value "". For XML Schema [XML Schema Part 1] , applications must use the value "". Other types of resources are outside the scope of this specification and therefore should recommend an absolute URI in order to use this method.

namespaceURI String: The namespace of the resource being resolved, e.g. the target namespace of the XML Schema [XML Schema Part 1] when resolving XML Schema resources.

publicId String: The public identifier of the external entity being referenced, or null if no public identifier was supplied or if the resource is not an entity.

systemId String: The system identifier, a URI reference [IETF RFC 2396], of the external resource being referenced, or null if no system identifier was supplied.

baseURI String: The absolute base URI of the resource being parsed, or null if there is no base URI.

LSInput A LSInput object describing the new input source, or null to request that the parser open a regular URI connection to the resource.

This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields


Follow Google Developers on WeChat

Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a short survey?
Help us improve the Android developer experience. (April 2018 — Developer Survey)