The All Properties tab allows you to edit component property settings as they are stored in the EJB Server configuration repository. You can only modify or delete properties that you have added—you cannot modify or delete default properties, such as the Instance Timeout property.
To add a property:
Fill in the Add fields as follows:
Enter the property name in the Name field.
Enter the value in the Value field.
Click Add and then OK.
To delete a property:
Highlight the property you want to delete:
Click Delete and then OK.
The following component properties can be configured only from the All Properties tab:
com.sybase.jaguar.component.keys For an EJB entity Bean, specifies the name of an IDL typedef for a sequence of the Bean’s primary key structures. This type is used when generating the skeleton and implementation classes for the component.
When you manually specify a value for the Primary Key field
on the Persistence tab, EJB Server sets this property to module::componentKeys where module is
the module containing the primary key type, and component is
the component name. The Adaptive Server plug-in defines the type
if it does not exist, using the following structure:
typedef <sequence pk> componentKeys
where pk is the primary key type, and component is the component name.
Set the com.sybase.jaguar.component.keys property only when you have manually defined a sequence that uses another naming convention or that is located in another module.
If you have used PowerJ or the Adaptive Server plug-in import feature to import an entity Bean, the com.sybase.jaguar.component.keys typedef may use a different naming convention.
com.sybase.jaguar.component.tx_outcome Determines whether an exception is thrown to the client when a transaction is rolled back. Sybase recommends that you do not alter this setting.
com.sybase.jaguar.component.refresh This property specifies whether the component can be refreshed.
If the value is false, the
File | Refresh option has no effect for the component.
Allowable values are true and false.
The default is true.
com.sybase.jaguar.component.java.classes For Java components, this property lists additional java classes that must be reloaded when the component is refreshed. The property takes as values a list of fully qualified class names separated by commas. You can specify all classes in a package using wildcards, as in this example:
com.xyz.MyPackage.*
You can specify all classes in a JAR file by specifying the JAR file name, as in this example:
MyEntityBean.jar
The JAR file must be deployed in the $SYBASE/$SYBASE_EJB/java/classes subdirectory.
Copies of the specified classes must be deployed under one of the following locations. When loading classes required by Java components, EJB Server searches for classes in this order:
Any JAR file that is listed in the com.sybase.jaguar.component.java.classes property and deployed in the EJB Server SYBASE/$SYBASE_EJB/java/classes subdirectory.
The class tree based at the SYBASE/$SYBASE_EJB/java/classes subdirectory.
The class tree based at the SYBASE/$SYBASE_EJB/html/classes subdirectory.
com.sybase.jaguar.component.control Specifies the name of the IDL control interface. The control interface defines methods called by the EJB Server in response to changes in the instance lifecycle. The choices are summarized in this table:
Control interface |
Description |
|---|---|
JaguarEJB::EntityBean |
For EJB entity Beans. |
JaguarEJB::StatefulSessionBean |
For EJB stateful session Beans. |
JaguarEJB::StatelessSessionBean |
For EJB stateless session Beans. |
