Sprout Farmer
com.rims.sprout.util.DeployTool
Base Window
The base window is the starting point for the Sprout Farmer's user interface.
From here you are able to add descriptors to the list from the local hard drive,
remove one from the list, or create a new one. Displayed in the descriptor list
is the type of bean that the descriptor describes, as well as the deployment name
for that Enterprise Bean and the the filename of the descriptor in the list.
You may also choose to process the selected descriptor. This processing generates
the skeleton and stub classes for your bean as well as some supporting classes
required by the ServiceTango to deploy your Enterprise Bean. The status window at the
bottom of the window is used to display status messages as the classes are being
generated.
You may also change the global options for the Sprout Farmer by pressing the "Options"
button on the toolbar or by selecting Edit|Options from the menu.
Sprout Farmer Options
Several options can be configured via the Sprout Farmer Options dialog. Three
options currently exist. The Temporary Directory, RMIC Path, and the
Compile To directory.
- Temporary Directory - this directory is where the generated source files
are going to be kept. When a bean is deployed, generated .java files
are created for use by the ServiceTango. Where these are generated is
dictated by this option. The serialized descriptor files used to deploy
the bean in ServiceTango is also generated in this directory.
- RMIC Path - This is the full pathname of the rmic.exe file installed on your
system. This is NOT the rmic that comes with the JDK. This is the RMIC
that comes with ServiceTango. It should be in the bin directory under the
ServiceTango's installation directory.
- Compile To - This is your normal compilation directory. This directory should
exist in your class path. When starting the ServiceTango, SS will look in
this directory for the generated .class files that are created by the
Sprout Farmer.
Main Tab
The main tab is the start point for editing an individual Enterprise Bean descriptor.
There are several entries on this tab that must be filled in to deploy a bean
properly.
- Enterpise Bean Type - Determines whether the bean is an Entity or a Session Bean
- Bean Deploy Name - The name that will be registered in the Naming Service and which
is used to perform look ups on the Bean's Home interface.
- Home Class - This is the interface of the Enterprise Bean. This must
extends javax.ejb.EJBHome
- Remote Class - This is the remote interface of the Enterprise Bean. This must
extend javax.ejb.EJBObject
- Bean Class - The bean's implementation. This must implement either javax.ejb.SessionBean
or javax.ejb.EntityBean.
- Primary Key Class - For an entity bean, this class denotes the class that
contains the Primary Key attributes for an the entity bean.
- Serialized File - The name of the serialized file to be created, w/o the suffix.
- Protocol - The protocol that the bean will be deployed under. Currently, only
IIOP is supported.
Entity Attributes
For an entity bean, a one to one mapping exists between an entity bean and a database table.
For each instance of an entity bean, that bean needs to be populated with data from
the database table. In order to do this, the entity bean's attributes must be matched
to column names from the database. This is the screen that allows you to do just that.
Finders
This is the tab used for specifying the finder methods of the home interface
and how the SQL is generated to retrieve the entities from the database.
Methods
Deployment