Schema for Geronimo Services deployment plans.
Instance documents should begin with the element:
>gbeans xmlns="http://geronimo.apache.org/xml/ns/deployment-1.0"<
You are required to specify either parentId or both domain and server. domain and server form
the domain and J2EEServer key for gbeans in this configuration and any descendant configurations.
"import" holds a URI, where the URI matches the configId of another configuration.
That configuration will be added as a parent of this configuration (the main
impact being that it's ClassLoader will be a parent of the ClassLoader for this
configuration.
Generally this URI will have the Maven form (groupId/artifactId/version/type),
and you can also use the sub-elements (groupId, type, ...) accordingly.
However, if you deploy a custom module with a simple configId like "Foo",
you can use that as the URI value here, and in that case you could not use the
subelements because you wouldn't have values for all of them.
"include" holds a URI, where the URI identifies an entry in the server's Repository.
When this module is being built, the content of that repository entry will be
copied into this module and added to the ClassPath of this module. This is
currently only supported for a small number of module types, and is typically used
to create more "standalone" modules that don't need a populated repository to run.
This URI must always have a form acceptable to the Repository, which currently
takes Maven-style URIs (groupId/artifactId/version/type). You can also use the
sub-elements (groupId, type, ...) instead of a full URI.
"dependency" holds a URI, where the URI identifies an entry in the server's
Repository. That repository entry will be added to the ClassPath of this module.
Essentially, this module's ClassPath points to that location in the server's
repository, so that entry must be in the repository at runtime for this to work.
This URI must always have a form acceptable to the Repository, which currently
takes Maven-style URIs (groupId/artifactId/version/type). You can also use the
sub-elements (groupId, type, ...) instead of a full URI.
A list of classes which will never be loaded from parent ClassLoaders of this
module. For example, if Log4J was listed here, the module would never see
Geronimo's copy of Log4J. If the module provided it's own Log4J JAR it would
use that, otherwise it would not be able to load Log4J at all.
The form of this is a comma-separated list of fully-qualified class names or
prefixes. Essentially, any class that starts with one of the prefixes listed
here will be treated as hidden. For example, if you set this value to
"java.util,java.lang" then you would really screw up your application. :)
A list of classes which will only be loaded from parent ClassLodaers of this
module (never from the module's own ClassLoader). For example, this is used
to prevent a web application from redefining "javax.servlet", so those
classes will *always* be loaded from the server instead of from the web
web application's own ClassPath.
The form of this is a comma-separated list of fully-qualified class names or
prefixes. Essentially, any class that starts with one of the prefixes listed
here will be treated as hidden. For example, setting this to
"javax.servlet,javax.ejb" would protect some of the core J2EE classes from
being overridden.
Adds a new custom component to the server. The component will be deployed
when this application module is deployed, but it is not in any way protected,
so once it is up and running, other modules can refer to it normally.
postgresql/postgresql-8.0-jdbc/313/jar
2.
postgresql
jar
postgresql-8.0-jdbc
313
]]>
This group contains the components of a jsr-77 object name