Editing the General Settings of an Enterprise Bean 

Procedure

If you want to modify the general settings of an existing enterprise bean, you will have to click the Edit button first. The fields in the pane will become enabled.

       1.      Click the General tab.

       2.      Specify a name of the bean in the Bean Name field.

       3.      Specify the fully qualified bean class name in the Bean Class field. You can choose from the drop down box of the available names, or enter your own one.

These options, as well as the ones in the other fields are taken from the locations pointed to by the project classpath.

A fully qualified class name consists of the name of the enterprise bean and the package from the project path.

       4.      Specify the settings of the bean according to its type (entity bean, session bean and message-based bean).

       5.      Click the Check button to confirm your changes. All fields will become disabled.

       6.      Depending on the type of bean you create, you will have to provide different information for the bean.

Specifying Entity Bean Settings

..

       1.      Enter the fully qualified entity bean names of the remote home and remote interface in the Remote Home Interface and the Remote Interface dropdown boxes, or choose from the suggested names.

       2.      Enter the fully qualified entity bean names of the local home and local interfaces in the Local Home Interface and Local Interface dropdown boxes, or choose from the suggested names.

       3.      Specify the key field of the enterprise bean in the Primary Key Field field.

If you define a compound primary key class, the Primary Key field must be empty. In case of unknown primary key, the Primary Key field is empty and the primary key is set to java.lang.Object.

       4.      Specify the key field type of the enterprise bean in the Primary Key Type field.

       5.      Specify the manager of the bean persistence in the Persistence Management field. It could be either Bean Management or Container Management. If you choose the Container Management option, you will also have to:

                                                  i.       Specify the version of the Container Managed Persistent Bean in the Cmp Version field. If you use EJB version 1.1 bean classes and interfaces, you should select the 1.x option. If you use EJB version 2.0 bean classes and interfaces, you should select the 2.x option.

                                                ii.       Specify a name for the schema type in the Schema Name field. Set this name for CMP bean v2.x only.

If you do not specify a schema name, the bean name is set by default.

       6.      Select the Reentrant checkbox if the bean should accept concurrent calls.

Specifying Session Bean Settings

...

       1.      Enter the fully qualified entity bean names of the remote home and remote interfaces in the Remote Home Interface and the Remote Interface dropdown boxes, or choose from the suggested names.

       2.      Enter the fully qualified entity bean names of the local home and local interfaces in the Local Home Interface and Local Interface dropdown boxes, or choose from the suggested names.

       3.      Specify the demarcation type of the bean. You can do this by selecting an option from the Demarcation Type dropdown box. You can choose between the Container and Bean options.

       4.      Specify the management type of the bean. You can do this by selecting an option from the Management Type dropdown box. You can choose between the Stateless and Stateful options.

Specifying Message-Based Bean Settings

...

       1.      Specify the demarcation type of the bean in the Demarcation Type dropdown box. You can choose between the Container and the Bean options. If you choose a Container demarcation type, you do not need to specify a message acknowledgement type.

       2.      If you choose a Bean demarcation type, then you can specify a message acknowledgement type in the Acknowledgement dropdown box. You can choose between:

·        Auto-acknowledge – the JMS AUTO_ACKNOWLEDGE semantics will be used.

·        Dups-ok-acknowledge – the JMS DUPS_OK_ACKNOWLEDGE semantics should be used.

If you do not specify an acknowledgement type, the Auto acknowledge will be used.

       3.      Specify the type of the JMS destination in the Destination Type dropdown box.

       4.      If you want to use a durable subscription, then selec the Durable Subscriber checkbox. Otherwise, leave it empty.

       5.      If you use a durable subscription, enter in the Subscription Name field the name of the subscriber who will use it.