Package properties

Description

Package property names begin with com.sybase.jaguar.package. A package allows you to group related components together for the purpose of access control or configuration. In EAServer Manager, configure package properties in the Package Properties dialog box.




com.sybase.jaguar.description

Description

Specifies a text description of the package.

Syntax

desc

Where desc is the descriptive text.

Usage

In EAServer Manager, set this property using the Description field on the General tab of the Package Properties dialog box.




com.sybase.jaguar.package.application

Description

Specifies the application that this package is installed in, if any.

Syntax

The name of the application. If not set, the package is not in an application and may be installed directly in one or more servers.

Usage

A package may be installed in one application or one or more servers. A package installed in an application may not be installed directly in a server or in another application.

In EAServer Manager, set this property by installing the package in an application or removing the package from an application.

See also

com.sybase.jaguar.application.packages




com.sybase.jaguar.package.classloaderpolicy

Description

Specifies how the custom class loader (version 2) resolves version conflicts when you specify the same class at multiple levels in the class loader hierarchy.

Syntax

Same as com.sybase.jaguar.application.classloaderpolicy.

See also

com.sybase.jaguar.server.jvm.classloader, com.sybase.jaguar.application.classloaderpolicy, com.sybase.jaguar.component.classloaderpolicy, com.sybase.jaguar.webapplication.classloaderpolicy

Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.




com.sybase.jaguar.package.code.set

Description

Specifies the default for the com.sybase.jaguar.component.code.set component property.

Syntax

Same as com.sybase.jaguar.component.code.set. The default is the server property com.sybase.jaguar.server.code.set.

Usage

In EAServer Manager, set this property using the Advanced tab in the Package Properties dialog box.

See also

com.sybase.jaguar.component.code.set, com.sybase.jaguar.server.code.set




com.sybase.jaguar.package.DOMfactory

Description

Specifies the class name for a custom DOM XML parser factory class.

Syntax

The class name. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.package.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.

See also

com.sybase.jaguar.package.SAXfactory, com.sybase.jaguar.package.XSLTfactory




com.sybase.jaguar.package.files

Description

Specifies files to be included when the package is exported to a Jaguar JAR archive or replicated to another installation using synchronization.

Syntax

Same as for com.sybase.jaguar.applicationclient.files. A package archive includes files for installed components, plus those specified by this property.

See also

com.sybase.jaguar.package.files.corbastubs, com.sybase.jaguar.package.files.ejbstubs, com.sybase.jaguar.component.files




com.sybase.jaguar.package.files.corbastubs

Description

Specifies the files that implement Java/CORBA stubs for the components in the package.

Syntax

Set when Java/CORBA stubs are generated. Do not modify.

See also

com.sybase.jaguar.package.files, com.sybase.jaguar.package.files.ejbstubs, com.sybase.jaguar.component.files.corbastubs




com.sybase.jaguar.package.files.ejbstubs

Description

Specifies the files that implement EJB stubs for the components in the package.

Syntax

Set when EJB stubs are generated. Do not modify.

See also

com.sybase.jaguar.package.files, com.sybase.jaguar.package.files.corbastubs, com.sybase.jaguar.component.files.ejbstubs




com.sybase.jaguar.package.java.classes

Description

Specifies Java classes and JAR files to be loaded by the package’s custom class loader.

Syntax

Same as for com.sybase.jaguar.application.java.classes.

Usage

See “Custom class lists for packages, applications, or servers” in Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.

In EAServer Manager, set this property using the Java Classes tab in the Package Properties dialog box.

See also

com.sybase.jaguar.component.java.classes, com.sybase.jaguar.application.java.classes, com.sybase.jaguar.server.java.classes




com.sybase.jaguar.package.name

Description

Specifies the package name.

Syntax

pack-name

Where package-name is the application name.

Usage

In EAServer Manager, the package name is set when creating or importing a package and cannot be changed.




com.sybase.jaguar.package.roles

Description

Specifies roles that a user must belong to in order to invoke the components (other than EJB components) installed in this package.

Syntax

role1, role2, ...

Where role1, role2, and so forth are role names defined in the repository.

Usage

In EAServer Manager, set this property using the File menu for the Roles folder displayed below the package icon.

Roles are attached to EAServer packages, components, and methods. Attaching a role to a package controls access to all non-EJB components in the package. Attaching a role to a component constrains access to all methods in the component’s interfaces. Attaching a role to a method constrains access to that method.

For EJB components, configure access control at the method level by setting the method property com.sybase.jaguar.method.security-roles for each method.

See also

com.sybase.jaguar.component.roles, com.sybase.jaguar.method.roles, com.sybase.jaguar.method.security-roles




com.sybase.jaguar.package.runasidentity.<id>

Description

Maps an identity name used in EJB (1.0 and 2.0) component configuration to an identity defined in the EAServer repository.

Syntax

Specify the identity referenced in EJB component configuration in the property name, for example:

com.sybase.jaguar.package.runasidentity.ejbFooId

Specify the mapped EAServer identity as the value, for example:

fooId

Usage

In EAServer Manager, you can set and view this property using the Run As Identity tab in the Component Properties dialog box, when the component type is an EJB 1.0 or 2.0 component that is installed in this package.

See also

Security properties, com.sybase.jaguar.component.runasidentity, com.sybase.jaguar.component.security.runasidentity




com.sybase.jaguar.package.SAXfactory

Description

Specifies the class name for a custom SAX XML parser factory class.

Syntax

The class name. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.package.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.

See also

com.sybase.jaguar.package.DOMfactory, com.sybase.jaguar.package.XSLTfactory




com.sybase.jaguar.package.security-role.<j2ee-role>

Description

Specifies a mapping from a J2EE role name used in the package to a role defined in the EAServer repository.

Syntax

com.sybase.jaguar.package.security-role.j2ee-role=jag-role

Where:

Usage

In EAServer Manager, set this property using the Role Mapping tab in the Package Properties dialog box.

Role names may also be specified at the component or application level.

See also

com.sybase.jaguar.package.security-roles, com.sybase.jaguar.application.security-roles, com.sybase.jaguar.component.security-role-ref.<j2ee-role-ref>, com.sybase.jaguar.component.security-role-refs




com.sybase.jaguar.package.security-roles

Description

Specifies logical J2EE role names used in the package.

Syntax

role1, role2, ...

Where role1, role2, and so forth are of the form:

(description=role-desc, name=role-name)

Where role-desc is an optional description of the role, and role-name is the name used in the application.

Usage

In EAServer Manager, set this property using the Role Mapping tab in the Package Properties dialog box. Each J2EE role name must be mapped to an EAServer role name by setting or creating the corresponding com.sybase.jaguar.package.security-role.<j2ee-role> property.

J2EE role names may also be specified at the component or application level.

See also

com.sybase.jaguar.package.security-role.<j2ee-role>, com.sybase.jaguar.application.security-role.<j2ee-role>, com.sybase.jaguar.component.security-role-ref.<j2ee-role-ref>, com.sybase.jaguar.component.security-role-refs




com.sybase.jaguar.package.XSLTfactory

Description

Specifies the class name for a custom XSLT XML parser factory class.

Syntax

The class name. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.package.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.

See also

com.sybase.jaguar.component.DOMfactory, com.sybase.jaguar.component.SAXfactory




schema:<schema-name>

Description

Specifies the EJB 2.0 (or later) component that represents a schema name used in EJB-QL queries.

Syntax

schema:schema-name=package/component

Where:

Variable

Specifies

schema-name

The schema name used in EJB-QL queries

package

The package that contains the component

component

The component name

If not set, the default is this-package/schema-name, where this-package is the package name, and schema-name is the schema name used in the EJB-QL query.

Usage

EJB-QL queries are used in EJB 2.0 entity beans that require container-managed persistence.

See also

Chapter 27, “Creating Entity Components,” in the EAServer Programmer’s Guide