| Refers to either another module running in the server, or
an entry in the server's Repository. In either case this effectively uses a
URI.
When this is pointing to a repository entry, the URI must have a form
acceptable to the repository, which is currently a URI consisting of
Maven-style identifiers separated by slashes (groupId/artifactId/version/type,
for example, the URI "postgresql/postgresql-8.0-jdbc/313/jar" for a file like
"repository/postgresql/postgresql-8.0-jdbc-313.jar").
When this is pointing to a module, the URI should match the
module's moduleId. This also looks
like a Maven-style URI discussed above.
The artifactType element can take either a straight URI (as in the examples
above), or maven-style identifier fragments (groupId, type, artifactId, and
version), which it will compose into a URI by adding up the fragments with
slashes in between.
There is a correspondence between the xml format and a URI. For example, the URI
postgresql/postgresql-8.0-jdbc/313/jar
corresponds to the xml:
postgresql
postgresql-8.0-jdbc
313
jar
Java class for artifactType complex type.
The following schema fragment specifies the expected content contained within this class.
<complexType name="artifactType">
<complexContent>
<restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
<sequence>
<element name="groupId" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/>
<element name="artifactId" type="{http://www.w3.org/2001/XMLSchema}string"/>
<element name="version" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/>
<element name="type" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/>
</sequence>
</restriction>
</complexContent>
</complexType>
|
