EDOBE XDOM PMML Manual do Utilizador descarregar pdf (Página 13)

extension.xml

Files

If the file extension.xml exists within an extension subdirectory, it

must be an XML file that describes exactly which files compose the

extension. This allows extension files with arbitrary names (other than

extension.jar, etc), or multiple Java jar and library files, as well as

some other specialized features.

An extension.xml file is exactly like an XTProps object file. Here is

an example:

<?xml version="1.0" encoding="UTF-8"?>

</Property>

</XTProps>

</IMML>

Each top-level property (like jarFile, libraryFile) can have one or

more values. If there is only one value, it can be specified in the same

<Property> clause, as with the libraryFile and explorerFile

peoprties above. If a property have multiple values, they are listed in

subproperties, as with the

jarFile property above.

Most of the property values are file names. Each file name may be an

absolute file, or a file name relative to the extension subdirectory. The

special file name

“.” stands for the extension subdirectory itself.

The property names recognized are:

•

explorerFile: Value is one or more Explorer IML files. Each

IML file defines a new Explorer tab with one or more nodes.

•

jarFile: Value is one or more Java jar files containing code

for the extension. One or more of the values may be a

directory, in which case the directory itself is used to search

for Java

.class files for individual classes. For example, if an

extension only used the single Java class

temp in the default

package, one could put the class file temp.class in the

extension subdirectory, and specify the jarFile property as

“.”. This may be useful during development.

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 97 98

Sem comentários

EDOBE XDOM PMML Manual do Utilizador Página 13