The component files are named according to this syntax:
file |
file name |
|---|---|
component skeleton |
component-name.c |
method prototypes |
component-name.h |
method implementation |
method-name.c.new |
create routine template |
create.c.new |
destroy routine template |
destroy.c.new |
where
component-name is the name of the component that you defined in EAServer Manager.
method-name can be either of the following:
If you did not specify a name in the Method file name field, files are generated for each method that you defined in EAServer Manager.
If you did specify a method file name, that name is used, and all methods are defined in this file. When specifying a file name, leave off the .c extension.
EAServer Manager creates the directory structure based on the code base that you specify and the component name, as follows:
code_base/jcts_skel/component_name
where:
code_base is the directory name that you specify for the Code Base field in EAServer Manager. If the specified value was not a full path, the directory will be located under the EAServer installation directory, relative to the html/classes subdirectory.
component_name is the component name as displayed in EAServer Manager.
