background image
<< Variables Used in COM/VB Scenario Test Templates | Replacement Variables for Stub Generation >>
<< Variables Used in COM/VB Scenario Test Templates | Replacement Variables for Stub Generation >>

Variables Used in EJB Scenario Test Templates

Replacement Variables for Scenario Test Generation Templates
131
Variables Used Only in the EJB Scenario Test Templates
The following table lists the replacement variables that are used only in the EJB
templates for scenario test generation:
<
COCLASS
_
PROGID
>
Coclass_progID, or programmatic
identifier, is a registry entry that is
associated with a CLSID. Like the CLSID,
the coclass_progID identifies a class, but
with less precision.
Example: Rose Operation := "Logical
View::COM::MyComponent::_Account::Po
st" Rose Interface := "Logical
View::COM::MyComponent::_Account"
Rose CoClass := "Logical
View::COM::MyComponent::Account"
Before: Set obj = CreateObject("<prog_id>")
After: Set obj =
CreateObject("MyComponent.Account")
Com_scenario_constructor
<
LIBRARY
_
NAME
>
Name of the COM Library associated with
the Rose Interface Class associated with the
operation.
Com_scenario_constructor
<
OBJECT
_
NAME
>
Variable that gets populated with the name
of the object instance (target object) in the
interaction diagram. If the name of the
target object is not present (it is not
required), then the variable is populated
with a concatenation of the COM library
name and the coclass name.
Com_scenario_constructor
Variable
Description
Template
Variable
Description
Templates Used In
<
OPERATION
_
SIGNATURE
>
In Java/EJB this is the
entire signature of an
operation call including the
concatenation of the
operation name and its
argument list.
Scenario_java_method1
Scenario_java_method2
<
HOME
_
INTERFACE
_
NAME
> The name of the home
interface.
Weblogic_scenario_constructor
Websphere_scenario_constructor
sunj2ee_scenario_constructor