Elements in config.xml

The following table describes each element that can be used in the configuration document. It also specifies how many times you can use each element in your config.xml file for a particular platform.

Element Description Occurrences
<access> Specifies that a BlackBerry WebWorks app can access external network resources. zero or more
<author> Specifies the author's name. one
<content> Specifies the application start page. one
<description> Specifies a human-readable description of the application. zero or more
<icon> Specifies an icon that represents the application on the Home screen of the BlackBerry device. zero or more
<license> Specifies end user license and copyright information. one or none
<name> Specifies a human-readable name for the application. one or more
<platform> Contains platform-specific configurationn information for your app.  
<preference> Defines a preference for the blackberry.app plugin (for example, screen orientation). zero or more
<rim:action> Specifies the actions that are associated with the invocation target. one or more
<rim:filter> Specifies the target filter. For each target, filters must be declared to describe the kinds of unbound invocation they support. zero or more
<rim:invoke-target> Registers your application as a handler for an invocation event. zero or more
<rim:mime-type> Defines a valid MIME type for the data. one or more
<rim:permissions> Provides a container for <rim:permit> to specify application permissions for device features. one
<rim:permit> Defines application permissions for device features. Must be a child of <rim:permissions>. one or more
<rim:property> Defines the types of URIs or files that are used to register an unbound invocation. zero or more
<rim:splash> Specifies the image to display on the screen while your application loads. zero or more
<rim:type> Defines the type of the invocation target. one
<widget> Provides a container for all other elements. one

Last modified: 2014-10-09



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus